You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How often does it reproduce? Is there a required condition?
No response
What is the expected behavior?
I would expect it to show the RTSP method, as https://nodejs.org/dist/latest-v18.x/docs/api/http.html#messagemethod doesn't seem to say that the method is not defined if it is RTSP instead of HTTP. If that is expected behavior, perhaps just a documentation update is in order.
What do you see instead?
That req.method is undefined
Additional information
Is there any way to tell if an incoming request is RTSP rather than HTTP?
The text was updated successfully, but these errors were encountered:
llhttp knows RTSP (kind of) but see nodejs/llhttp#103 for why it doesn't work. I don't know if this can be fixed without reintroducing the original issue. Probably best to simply document it.
Version
v18.5.0
Platform
Microsoft Windows NT 10.0.19044.0 x64
Subsystem
http
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
No response
What is the expected behavior?
I would expect it to show the RTSP method, as https://nodejs.org/dist/latest-v18.x/docs/api/http.html#messagemethod doesn't seem to say that the method is not defined if it is RTSP instead of HTTP. If that is expected behavior, perhaps just a documentation update is in order.
What do you see instead?
That
req.method
isundefined
Additional information
Is there any way to tell if an incoming request is RTSP rather than HTTP?
The text was updated successfully, but these errors were encountered: