-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
UnsupportedWarning: Status message is not supported by HTTP/2 (RFC7540 8.1.2.4) #1253
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
Comments
Yes and no. Setting the message is done currently so removing that would arguably be breaking. One could remove setting the message for HTTP/2 but that would require Koa to know what server it's running on - uncool. We could make it flag-able, e.g. |
What if our app is running using both http and http2? Would we need two separate apps with different flag values? |
With that solution, yes. But I agree - it's not elegant. Sort of off topic but it feels like Koa needs a grand vision on how to support http/2 before an effort is put to fully support it (and I'm probably not the right person to envision that). Specifically how the flow of pushing should be implemented. I almost feel like there needs to be another level of abstraction between Koa and server to keep Koa agnostic (without going |
use const server = spdy.createServer(options, app.callback()) |
do not use http2 module in the nodejs core, use spdy node node:8.12.0-jessie |
Solved by #1264 |
Hi
I tried to use the koa 2.5.3 framework on http2, but when the client accesses a url that does not exist, it will trigger the "UnsupportedWarning: Status message is not supported by HTTP/2 (RFC7540 8.1.2.4)" warning.
This seems to be because koa is set or gets response.statusMessageRelated source code
Is there any way to solve it?
The text was updated successfully, but these errors were encountered: