-
Notifications
You must be signed in to change notification settings - Fork 9
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
weird on Spicy HTTP analyzer with websocket traffic #99
Comments
FTR, the weird this triggers is
That part of the grammar is public type Replies = unit {
%port = 80/tcp &responder;
: Reply[];
}; What this means that parsing of Since a Websocket negotion starts with a request to switch the protocol and the remove responding with a To support parsing traffic with e.g., Websockets one would need to add to this grammar support for |
Thanks, How do we switch from HTTP analyzer to another one ? When I wrote websocket analyzer in Binpac (for Bro) I record websocket analyzer as a son of HTTP. Thank you for your help. |
After research, I think I have to implement the same behavior that in the native HTTP analyzer with upgrade_connection, updated and others variables. For that, I think to use %context because these variables are set across session (http headers and status code). How can I access in the context of a unit above another ? Thanks for your help |
Hi,
Will working on websocket analyzer in spicy (zeek/zeek#1637) I find that the HTTP analyzer give a parse error with websocket traffic.
I try to replay zeek btest (101-switching-protocols) with spicy analyzer to confirme.
the new btest file :
basic.zeek.txt
and the weird log file that result:
weird.log
Any ideas to solve this ?
The text was updated successfully, but these errors were encountered: