It's proving slightly more involved than I expected to get a solid Netty patch together, Stephen -- looks like it'll take me a little longer. We basically just need to make the protocol version modifiable in DefaultHttpResponse/HttpMessage and change it in HttpMessageDecoder when we add chunked encoding, but fatigue is getting the best of me. Should be done soon though.<div>
<br></div><div>-Adam</div><div><br><br><div class="gmail_quote">On Mon, Nov 2, 2009 at 8:32 AM, Adam Fisk <span dir="ltr"><<a href="mailto:a@littleshoot.org">a@littleshoot.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Fantastic catch, Stephen! I'll have to add it in to LittleProxy this<br>
evening - running around a bit today. Seems like a patch to<br>
HttpResponseDecoder is in order, and I can tackle that if you don't<br>
get to it first. I'm also happy to give you commit permissions if you<br>
like. This in particular is clearly a Netty and not a LittleProxy<br>
issue, but I can give you access to the repo if you need to make any<br>
changes going forward.<br>
<br>
Thanks for taking the time.<br>
<font color="#888888"><br>
-Adam<br>
</font><div><div></div><div class="h5"><br>
<br>
On Mon, Nov 2, 2009 at 7:23 AM, Stephen Haberman<br>
<<a href="mailto:stephen@exigencecorp.com">stephen@exigencecorp.com</a>> wrote:<br>
><br>
>> The hard part is the testing cycles. I'm thinking it might make the<br>
>> most sense to just run a server that returns that file for every<br>
>> request, completely bypassing Netty and allowing us to easily tweak<br>
>> details of the response.<br>
><br>
> Yeah, that is what netcat allowed me to do--it took the raw bytes in the<br>
> file (e.g. headers + content) and dumped them onto the wire when the<br>
> browser hit <a href="http://localhost:8080" target="_blank">http://localhost:8080</a>. So then I could edit the file,<br>
> run netcat, hit it with the browser, etc.<br>
><br>
> Turns out it's the HTTP version--change the first line of the response<br>
> from:<br>
><br>
> HTTP/1.0 200 OK<br>
><br>
> To:<br>
><br>
> HTTP/1.1 200 OK<br>
><br>
> And firefox loads it successfully now.<br>
><br>
> Makes sense, in that transfer encoding must be a HTTP 1.1 feature, and<br>
> the originating server was sending it as a HTTP 1.0 complaint request,<br>
> but the proxy upgrades it to an HTTP 1.1 request without bumping the<br>
> version number.<br>
><br>
> - Stephen<br>
><br>
> _______________________________________________<br>
> netty-users mailing list<br>
> <a href="mailto:netty-users@lists.jboss.org">netty-users@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/netty-users" target="_blank">https://lists.jboss.org/mailman/listinfo/netty-users</a><br>
><br>
<br>
<br>
<br>
</div></div><div><div></div><div class="h5">--<br>
Adam Fisk<br>
<a href="http://www.littleshoot.org" target="_blank">http://www.littleshoot.org</a> | <a href="http://adamfisk.wordpress.com" target="_blank">http://adamfisk.wordpress.com</a> |<br>
<a href="http://twitter.com/adamfisk" target="_blank">http://twitter.com/adamfisk</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Adam Fisk<br><a href="http://www.littleshoot.org">http://www.littleshoot.org</a> | <a href="http://adamfisk.wordpress.com">http://adamfisk.wordpress.com</a> | <a href="http://twitter.com/adamfisk">http://twitter.com/adamfisk</a><br>
</div>