Skip to content
This repository has been archived by the owner on Apr 12, 2024. It is now read-only.

fix($http): don't covert 0 status codes to 404 for non-file protocols #6504

Closed

Conversation

pkozlowski-opensource
Copy link
Member

PR #5547 introduced conversion of all 0 status codes to 404 for cases
where no response was recieved (previously this was done for the
file:// protocol only). But this mechanism is too eager and
masks legitimate cases where status 0 should be returned. This commits
reverts to the previous mechanism of handling 0 status code for the
file:// protocol (converting 0 to 404) while retaining the returned
status code 0 for all the protocols other than file://

Fixes #6074
Fixes #6155

PR angular#5547 introduced conversion of all 0 status codes to 404 for cases
where no response was recieved (previously this was done for the
file:// protocol only). But this mechanism is too eager and
masks legitimate cases where status 0 should be returned. This commits
reverts to the previous mechanism of handling 0 status code for the
file:// protocol (converting 0 to 404) while retaining the returned
status code 0 for all the protocols other than file://

Fixes angular#6074
Fixes angular#6155
@mary-poppins
Copy link

Thanks for the PR! Please check the items below to help us merge this faster. See the contributing docs for more information.

  • Uses the issue template (#6504)

If you need to make changes to your pull request, you can update the commit with git commit --amend.
Then, update the pull request with git push -f.

Thanks again for your help!

@leifhanack
Copy link

+1

@leifhanack
Copy link

Any idea when this will be merged? Is it shortly or should I patch angular on my own for a while? Thanks, Leif

@create-renegr
Copy link

I am interested in this as well. Any ideas when this is going to happen? Thanks in advance!

@quicksnap
Copy link

+1 -- we're affected by this as well! Please merge.

@vojtajina
Copy link
Contributor

Thanks @pkozlowski-opensource this looks good to me.

Merged as 56e73ea

@vojtajina vojtajina closed this Mar 14, 2014
@leifhanack
Copy link

@vojtajina thanks a lot, will you spend a 1.2.15 now or when is the release scheduled?! regards, leif

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
7 participants