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.

Sign up for GitHub

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

Jump to bottom

"Network error" != "non 200 http status code" #1009

Closed
shs96c opened this issue Aug 16, 2017 · 0 comments
Closed

"Network error" != "non 200 http status code" #1009

shs96c opened this issue Aug 16, 2017 · 0 comments
Assignees
@shs96c
Milestone
Level 1

Comments

@shs96c
Copy link
Contributor

shs96c commented Aug 16, 2017

In chapter 9. Navigation:

response is a network error

We should make clear that this isn't a problem with a completed HTTP request, but something else, such as a timed out connection. Refer to the ISO model, perhaps?
@shs96c shs96c added this to the Level 1 milestone Aug 16, 2017
@shs96c shs96c mentioned this issue Aug 16, 2017
Open
2 tasks
shs96c added a commit to shs96c/webdriver-spec that referenced this issue Aug 16, 2017
@shs96c
Clarify that network error and unsucessful HTTP result aren't the same
6f220fa 
Closes w3c#1009
@shs96c shs96c mentioned this issue Aug 16, 2017
Merged
@shs96c shs96c self-assigned this Aug 17, 2017
AutomatedTester pushed a commit that referenced this issue Aug 17, 2017
@shs96c @AutomatedTester
Clarify that network error and unsucessful HTTP result aren't the same
9f9707b 
Closes #1009
jlipps pushed a commit to jlipps/webdriver that referenced this issue Oct 11, 2017
@shs96c @jlipps
Clarify that network error and unsucessful HTTP result aren't the same
20f48be 
Closes w3c#1009
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@shs96c shs96c

Labels
None yet
Projects
None yet
Milestone
Level 1
Development

No branches or pull requests
1 participant
@shs96c