Issue passing Authorization header in old Safari?
See original GitHub issueHi, I’m using the Authorization header with EventSource polyfill. Everything works great with Chrome, Firefox and recent Safari, but with Safari 9 the header is not sent to the server (it’s missing from the browser request). I see that only since Safari 10.1 the Fetch API is supported. Could this be the reason? And eventually is there anything I can do to fix/workaround the issue?
If it matters, I create the instance this way:
new EventSourcePolyfill(this.url, {
withCredentials: this.withCredentials,
lastEventIdQueryParameterName: 'last-id',
headers: { Authorization: 'Token the_token' },
});
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Why is Safari not clearing the Authorization header after HTTP ...
The same code running in Safari shows that the Authorization header was passed correctly in the request, but a debug output of the...
Read more >Safari, Authorization header hangs… | Apple Developer Forums
Safari, Authorization header hangs the request to the server XHR requests with Authorization header over HTTPS (both together) don't reach the server, using...
Read more >Safari Authorization header - Laracasts
I am using the basic api authentication which is working in chrome and locally in safari. On the live server safari is returning...
Read more >How to send Basic Authentication headers in Selenium?
I've tested using format http://user:pass@host and it works. So in Python (in setUp() of MyClass(unittest.TestCase) class) this should look like:
Read more >HTTP authentication - MDN Web Docs - Mozilla
Usually a client will present a password prompt to the user and will then issue the request including the correct Authorization header.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@Yaffle Nope, it’s client side. I still don’t know where exactly the mistake is, but a friend told me that before the last client refactoring (which was big) it stopped working.
It turned out it was an error in my code! Sorry for bothering, thanks for the polyfill.