| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
…in HTTP version <= 1.0
…in HTTP version <= 1.0
|
Looks non-intrusive enough. Can you add a test? And maybe point me to one or two servers that work like that? I'd like to test how other tools handle it. |
Sorry, something went wrong.
|
Hi, I don't know exactly how a test case of a notification callback should Best Regards, 2012.03.24. 13:50 keltezéssel, Ben Noordhuis írta:
|
Sorry, something went wrong.
|
Simple requests haven't been actively used since HTTP 0.9 and I know of nothing that sends them. Do you think this feature is valuable, @tomika? If so I'd be happy to write some tests for you. |
Sorry, something went wrong.
|
It's very kind of you. Unfortunately in corporate environments there are some dinosaurs I have to live with. I would be glad if you would be so kind and create the required test cases and the suggested patches (I already use for while) would be merged into main branch. Best Regards, |
Sorry, something went wrong.
FWIW, I know of at least one cable modem that sends HTTP 0.9 responses. |
Sorry, something went wrong.
|
I work for telco companies and have to communicate with HUAWEII devices (among many others). What else should I say more? ;o) |
Sorry, something went wrong.
|
This can be closed |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
A new notification callback is inserted called "status complete", that is called only when a valid status line read.
This way if a parse error occured and it is in the status line the message can be treated as a valid simple response. Collecting input until "status complete" callback and switch mode on error makes possible to handle this rare special case written in RFC-1945 Section 6.