I revisited the Stack Overflow post and it appears that I am able to receive HTTP responses properly now. Doing so required me to launch WireShark and copy a browser's actual headers. I also had to add a ContentDecoderAgent.
Specifically it was the lack of an Accept-Encoding that was causing the problem. I added ["gzip, deflate, sdch"] and it seemed to do the trick. I really do think that there should be an easier way to do this. I also don't understand why the Agent couldn't have properly interpreted the initial response. Thanks for everyone's time. On Mon, Apr 13, 2015 at 2:45 PM, Chris Drane <[email protected]> wrote: > Yes I actually started that thread, and I wasn't fully satisfied with the > answer. I feel like I was given workarounds rather than addressing what > seems to be a problem with how either HTTP or TCP is handled. Please > correct me if I'm mistaken (I probably am). > > On Mon, Apr 13, 2015 at 2:39 PM, Wolfgang Rohdewald < > [email protected]> wrote: > >> Am Montag, 13. April 2015, 14:29:01 schrieb Chris Drane: >> > I am new with Twisted so chances are that this is *not* a bug. If that >> is >> > the case, I would very much appreciate it if you help me understand >> what I >> > am doing incorrectly. >> >> just googled the error message out of curiousity: >> >> >> http://stackoverflow.com/questions/29423986/twisted-giving-twisted-web-client-partialdownloaderror-200-ok >> >> -- >> Wolfgang >> > >
_______________________________________________ Twisted-web mailing list [email protected] http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-web
