Announcing LittleProxy 0.1 based on Netty
Stephen Haberman
stephen at exigencecorp.com
Mon Nov 2 10:23:10 EST 2009
> The hard part is the testing cycles. I'm thinking it might make the
> most sense to just run a server that returns that file for every
> request, completely bypassing Netty and allowing us to easily tweak
> details of the response.
Yeah, that is what netcat allowed me to do--it took the raw bytes in the
file (e.g. headers + content) and dumped them onto the wire when the
browser hit http://localhost:8080. So then I could edit the file,
run netcat, hit it with the browser, etc.
Turns out it's the HTTP version--change the first line of the response
from:
HTTP/1.0 200 OK
To:
HTTP/1.1 200 OK
And firefox loads it successfully now.
Makes sense, in that transfer encoding must be a HTTP 1.1 feature, and
the originating server was sending it as a HTTP 1.0 complaint request,
but the proxy upgrades it to an HTTP 1.1 request without bumping the
version number.
- Stephen
More information about the netty-users
mailing list