truncated responses for some browsers?

5 views
Skip to first unread message

joesgroups

unread,
Mar 6, 2010, 9:03:54 AM3/6/10
to pylons-discuss
Hi,
I am running a very simple application with,

* pylons 0.9.7
* python2.5
* debian Etch 5.0

The application works fine but it seems to return truncated messages
for most web browsers, e.g. firefox, safari, chrome. The salient bit
of code is just,

return "http://www.google.com/search?test"

as part of an 'as-trivial-as-possible' test for a default
controller.

The result is that in firefox or safari the browser shows,

http://m.google.com/se

although the pylons log claims that it sent back the full response
string.

In the case of wget however, it returns the full string as
expected.

This is starting to drive me insane and I cannot figure out what is
going wrong. My best guess is that the content-length header is not
being set somewhere, but I'm not sure where or what I can possibly do
about it.

joesgroups

unread,
Mar 8, 2010, 4:53:03 PM3/8/10
to pylons-discuss
This seems like a pretty heinous error, is there really no feedback on
it? Is there any additional information I could supply?
Again this problem doesn't occur with wget, but occurs with most
browsers.
The available examples in the list for setting content-length in the
base controller do not work with this version of pylons, which throws
an error related to py_object missing.

Matt Feifarek

unread,
Mar 8, 2010, 5:24:03 PM3/8/10
to pylons-...@googlegroups.com
On Mon, Mar 8, 2010 at 3:53 PM, joesgroups <joes.mail...@gmail.com> wrote:
This seems like a pretty heinous error, is there really no feedback on
it?  Is there any additional information I could supply?
Again this problem doesn't occur with wget, but occurs with most
browsers.

To test your theory about content-length, try installing the FF extension "Live HTTP Headers" and you can see exactly what the server is sending to Firefox.

I haven't tested your problem myself. But I expect if wget is getting the correct data, so are the others. I expect that if they're NOT, something is happening on the wire somewhere... proxy perhaps?

I hope that this helps.

Matt Feifarek

unread,
Mar 8, 2010, 5:25:19 PM3/8/10
to pylons-...@googlegroups.com
On Sat, Mar 6, 2010 at 8:03 AM, joesgroups <joes.mail...@gmail.com> wrote:
return "http://www.google.com/search?test"


  The result is that in firefox or safari the browser shows,

http://m.google.com/se

This may be a typo, but you see that those are not just one truncated to the other, right? One is "www" and the other is "m". 

Something besides truncation is at work...
Reply all
Reply to author
Forward
0 new messages