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

Chrome/Opera (any OS) creates SPDY protocol errors on depth chart #22

Closed
mattheworres opened this issue Aug 16, 2016 · 4 comments
Closed
Labels

Comments

@mattheworres
Copy link
Owner

mattheworres commented Aug 16, 2016

This is OS independent (I've seen it on both Windows and OSX) and is on the latest version of Chrome. I can confirm it is not an issue with any plugins I have installed either, because a clean copy of Chrome produces the same issue.

The browser won't send the XHR requests to update the depth chart when a player is dragged to a new depth chart position. The request has a status of (failed), and the console gets an error message: PUT https://www.phpdraft.com/api/draft/59/pick/5026/depth_chart/37 net::ERR_SPDY_PROTOCOL_ERROR

This issue has been observed to also occur with the latest version of Opera, but not Firefox or Safari.

@mattheworres mattheworres changed the title Chrome (any OS) creates SPDR protocol errors on depth chart Chrome/Opera (any OS) creates SPDR protocol errors on depth chart Aug 16, 2016
@mattheworres mattheworres changed the title Chrome/Opera (any OS) creates SPDR protocol errors on depth chart Chrome/Opera (any OS) creates SPDY protocol errors on depth chart Aug 16, 2016
@mattheworres
Copy link
Owner Author

@zo0o0ot
Copy link
Contributor

zo0o0ot commented Aug 17, 2016

Upvoted 👍

@mattheworres
Copy link
Owner Author

So, my shared webhosting may be the culprit here. Looks like they have both SPDY and HTTP/2 protocols enabled on the server. SPDY is experimental and was deprecated once HTTP/2 came out, and in Chrome 51 they disabled support of it.

Webhost refuses to disable SPDY because they don't wish to disrupt their other customers, so I may be looking for alternate hosting (including Openshift).

@mattheworres
Copy link
Owner Author

Working on moving the site over to DigitalOcean this weekend in order to resolve this issue (should speed up the app 6x or more), but I will go ahead and close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants