Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(HTTP/XhrBackend): correctly set the status code on errors #9355

Merged
merged 1 commit into from
Jun 20, 2016

Conversation

vicb
Copy link
Contributor

@vicb vicb commented Jun 20, 2016

fixes #9329
fixes angular/http#54

@robwormald @jeffbcross could one of you please review ? Thanks

@vicb vicb added type: bug/fix action: review The PR is still awaiting reviews from at least one requested reviewer comp: http labels Jun 20, 2016
@vicb vicb added this to the 2.0.0-rc.3 milestone Jun 20, 2016
@@ -181,14 +181,30 @@ export function main() {
existingXHRs[0].dispatchEvent('error');
}));

it('should set the status and status code on error',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"status and statusText"

});
const xhr = existingXHRs[0];
xhr.setStatusCode(0);
xhr.setStatusText('');
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please add a comment that status=0 and statusText='' are common values for CORS related errors. otherwise we'll wonder what these are.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if we really care about the given values ? I'll add the comment anyway

@IgorMinar
Copy link
Contributor

please see comments above. otherwise lgtm

@vicb
Copy link
Contributor Author

vicb commented Jun 20, 2016

thanks for tge review. I have addressed your comment and will merge.

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: review The PR is still awaiting reviews from at least one requested reviewer cla: yes type: bug/fix
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Http: should return status code / text properly from errors
5 participants