v1.9.528 doesn't include credentials on chrome
See original GitHub issueWe had this code to get pdf through authenticated url
PDFJS.getDocument(url)
that breaks with version 1.9.528 on Chrome because it doesn’t include CSRF-TOKEN in the request. However, it works on firefox and safari. Now I have to fix it by enforce withCredentials: true. Does new version set the default of withCredentials to false?
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Fix issues with saved payment info & passwords - Android
You can save your contact, payment, and sign-in info to Chrome. If something doesn't work when you let Chrome remember your info, try...
Read more >Troubleshoot authentication & authorization issues
This page describes some common issues that you might encounter involving authentication and authorization. This app isn't verified.
Read more >Detect password leaks and breached credentials
Check for breached and/or leaked credentials. To check if a set of credentials has been compromised, query the Password Checkup database during assessments...
Read more >Chrome Browser Password Recovery for Windows - NirSoft
Be aware that in order to recover passwords created while you signed in with Microsoft account, you have to provide the random DPAPI...
Read more >How to clear basic authentication details in chrome
It seems chrome will always show you the login prompt if you include a username in the url e.g.. http://me@example.com. This is not...
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 FreeTop 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
Top GitHub Comments
Okay, from reading https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest/withCredentials, I have impression that to be compatible with XHR we need to use ‘same-origin’ instead of ‘omit’ there. I think it is safe in our context.
That’s how XHR worked before we introduced fetch().