No statusText on Chrome
See original GitHub issueSummary
The response should include status: 200
and statusText: "OK"
but Chrome returns the empty string in statusText
property.
Firefox is OK.
Steps to reproduce:
- copy
dist/axios.min.js
to console - paste following code to Chrome console
(async () => { const res = await axios.get(location.href); console.log('status', res.status); console.log('statusText', `"${res.statusText}"`); })();
Context
- axios version:
- v0.18.0
- v0.17.1
- Environment:
- Google Chrome (66.0.3359.117 64bit)
- Google Chrome (66.0.3359.139 64bit)
Issue Analytics
- State:
- Created 5 years ago
- Reactions:10
- Comments:8
Top Results From Across the Web
Why is the statusText of my XHR empty? - Stack Overflow
For some reason on Chrome statusTexts started to return empty as soon as we installed an SSL certificate in our server and url...
Read more >Response.statusText - Web APIs | MDN
The statusText read-only property of the Response interface contains the status message corresponding to the HTTP status code in ...
Read more >{“readyState”:0”responseText”:””,”status”:0:0,”statusText”:”error ...
Hello, I am having an issue where the tag app is no longer working on my Android device. My phone is running Android...
Read more >Response.statusText
The statusText read-only property of the Response interface contains the status ... Android webview, Chrome for Android, Edge Mobile, Firefox for Android ...
Read more >Change your availability status and mute notifications in ...
Status icon, Status text, Status meaning. "" Active, Gmail or Google Chat is open. "" Do not disturb. Google Chat notifications are muted....
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
Not only.
Drop
response.statusText
and useresponse.status
as solution.response.status >= 200 && response.status < 300
is more reliable.