-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
"SCHEME_DOMAIN_PORT is not defined" failures due to HTTP 500 all over websockets/ #10457
Comments
@jugglinmike, not sure if this will come up in your investigation, but a widespread failure like this is pretty easy to justify the time spending to fix... |
I'm assuming that a 500 can happen if there's no port defined for
|
config.default.json (read by tools/wptserve/wptserve/config.py) has:
I don't know what isn't working, though... |
Labelling this as roadmap and not urgent on the assumption that this has been broken a while. |
|
So not broken for so long, and my fault… |
@zcorpan |
OK, so it is |
The bug here is:
in |
I need to fix this to unbreak a gecko sync, so there will be a patch soon. |
Pinging for an update since this is marked Priority:urgent. |
Assigning to @jgraham as the urgency is on part of Gecko sync. |
I reviewed a patch last week by @jgraham. Should we not fix it upstream soon, even if the Gecko sync doesn't land? |
fixed in #10557 (which sadly didn't link here) |
As found in #1695 (comment), lots of tsets under websockets/ are failing. For example:
https://wpt.fyi/websockets/binary
In Chrome devtools I see "Failed to load resource: the server responded with a status of 500 (Internal Server Error)" so something pretty odd is happening here.
The text was updated successfully, but these errors were encountered: