Did Twitter ban the Google Chrome extension URI chrome-extension:// pattern when setting the oauth_callback parameter during https://api.twitter.com/oauth/request_token portion of OAuth handshake?
Reason I ask is twitter used to return chrome-extension://* URIs as expected using oauth_callback. Now it seems twitter is returning about:blank with breaks the OAuth dance.
Issue isn’t with URL Encoding because http:// returns as expected. The issue is twitter is actively targeting chrome-extension:// and with it Google Chrome extensions.
The URI twitter-extension:// no longer returns either (used too in our Unit tests), but at least shows this message: “Redirecting you back to the application. This may take a few moments. If your browser doesn’t redirect you please click here to continue” with the expected URI linked to “click here to continue”. However, the chrome-extension://* URI specifically redirects to about:blank and breaks OAuth entirely which means twitter is targeting to break OAuth handshake for Google Chrome extensions specifically.
It make Hulk mad!