wdenniss.com/in-app-browsers-and-rfc-8252

Preview meta tags from the wdenniss.com website.

Linked Hostnames

7

Search Engine Appearance

Google

https://wdenniss.com/in-app-browsers-and-rfc-8252

In-app browsers and RFC 8252

In 2016 I wrote RFC 8252 seeking to codify a new best practice on using the system browser (or in-app browser tabs) to perform OAuth flows, rather than a built-in WebView. A little history: you don't see this embedded WebView OAuth pattern much any more, but when I joined the Identity team at Goo



Bing

In-app browsers and RFC 8252

https://wdenniss.com/in-app-browsers-and-rfc-8252

In 2016 I wrote RFC 8252 seeking to codify a new best practice on using the system browser (or in-app browser tabs) to perform OAuth flows, rather than a built-in WebView. A little history: you don't see this embedded WebView OAuth pattern much any more, but when I joined the Identity team at Goo



DuckDuckGo

https://wdenniss.com/in-app-browsers-and-rfc-8252

In-app browsers and RFC 8252

In 2016 I wrote RFC 8252 seeking to codify a new best practice on using the system browser (or in-app browser tabs) to perform OAuth flows, rather than a built-in WebView. A little history: you don't see this embedded WebView OAuth pattern much any more, but when I joined the Identity team at Goo

  • General Meta Tags

    9
    • title
      In-app browsers and RFC 8252 – William Denniss
    • charset
      UTF-8
    • viewport
      width=device-width, initial-scale=1
    • robots
      max-image-preview:large
    • generator
      WordPress 6.7.3

  • Open Graph Meta Tags

    7
    • US country flagog:locale
      en_US
    • og:site_name
      William Denniss
    • og:title
      In-app browsers and RFC 8252
    • og:url
      https://wdenniss.com/in-app-browsers-and-rfc-8252
    • og:type
      article

  • Twitter Meta Tags

    4
    • twitter:title
      In-app browsers and RFC 8252
    • twitter:url
      https://wdenniss.com/in-app-browsers-and-rfc-8252
    • twitter:description
      In 2016 I wrote RFC 8252 seeking to codify a new best practice on using the system browser (or in-app browser tabs) to perform OAuth flows, rather than a built-in WebView. A little history: you don't see this embedded WebView OAuth pattern much any more, but when I joined the Identity team at Goo
    • twitter:card
      summary_large_image

  • Link Tags

    18
    • EditURI
      https://wdenniss.com/xmlrpc.php?rsd
    • alternate
      https://wdenniss.com/feed
    • alternate
      https://wdenniss.com/comments/feed
    • alternate
      https://wdenniss.com/in-app-browsers-and-rfc-8252/feed
    • alternate
      https://wdenniss.com/wp-json/wp/v2/posts/1608

Links

21