Error response (302) data unavailable in IE
See original GitHub issueSummary
Sending a JSON response with status code 302 and some payload from the server (Laravel 5.5) results in error.response.data
being undefined
in error handler on IE only (Chrome, Firefox, Safari, Opera do not seem affected, payload data is available as you would expect). error.response.request.response
and error.response.request.responseText
are empty string as well. Seems like IE is notorious for having these kind of issues
Context
- axios version: v0.17.0
- Environment: php v7.0.22, edge 16, windows 10
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:9
Top Results From Across the Web
302 Found: What It Is and How to Fix It - Airbrake Blog
A 302 Found message is an HTTP response status code indicating that the requested resource has been temporarily moved to a different URI....
Read more >HTTP 302 redirects between servers failing in IE, working in ...
I'm getting a blank white screen in IE when building a login system that redirects through a 3rd party server for authentication.
Read more >How to Fix 302 Found Error (5 Methods)
The HTTP error code 302 found indicates that a specific URL has been moved temporarily to a new location. Whenever visitors, Google robots,...
Read more >302 Status Code: What It Is + Its Impact on SEO - HubSpot Blog
The 302 status code is a redirection message that occurs when a resource or page you're attempting to load has been temporarily moved...
Read more >Power Query "From Web" not working - TechNet - Microsoft
Wikipedia says "The HTTP response status code 302 Found is a common way of performing URL redirection" What does Excel think it is?...
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
+1 Same issue in Chrome 75
When this issue will be resolved? By the way, this happens for me also on FF