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

Explicitly raise an error when server returns http 403 and dont continue #20

Merged
merged 1 commit into from
Apr 19, 2013
Merged

Explicitly raise an error when server returns http 403 and dont continue #20

merged 1 commit into from
Apr 19, 2013

Conversation

smoak
Copy link
Contributor

@smoak smoak commented Feb 5, 2013

Previously if the server returned a 403, eventsource would begin a retry
loop to connect to the server over and over. This loop will start before
a client can attach to the 'error' event because eventsource connects
right away in the constructor. This prevents client code from closing
the eventsource connection. This commit addresses this issue and fails
fast instead of allowing eventsource to enter a retry loop when a server
returns a 403.

Previously if the server returned a 403, eventsource would begin a retry
loop to connect to the server over and over. This loop will start before
a client can attach to the 'error' event because eventsource connects
right away in the constructor. This prevents client code from closing
the eventsource connection. This commit addresses this issue and fails
fast instead of allowing eventsource to enter a retry loop when a server
returns a 403.
@aslakhellesoy aslakhellesoy merged commit 7e49554 into EventSource:master Apr 19, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants