Well, we can write such utility on our own, but it will take some time
and will slow down other things we are working on.
I need some kind of HTTP-proxy like utility for Linux, which would just
tunnel requests through (no caching is required), but all HTTP request
and response headers will be logged (perferebly request and response
both stored in the same file).
I am starting to feel that only cure for Arachne cookie related problems
will be full implementation of HTTP/1.1. Unfortunately, it is not as
intuitive as HTTP/1.0, and I am not sure if useful subset of 1.1 can be
implemented as easily as subset of 1.0
If you know about such cookie trap, or if you know how to enable such
feature eg. in Squid, please let me know.
I am sure we can solve the cookie problem if we can compare exactly,
byte-by-byte, the difference between what Netscape is sending and what
Arachne is sending...
