When I visit my Seaside 2.8 based app using a Palm Pre webOS phone the
initial page renders okay but when I click on any link I see only the following. Any ideas? -Carl <html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml"> <head> <title>Error</title> </head> <body onkeydown="onKeyDown(event)" onload="onLoad()"> <h3>Transport<http> failed - Wrong response status line: Origin : http://irunbasic.com</h3> </body> </html> _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
2011/2/11 Carl Gundel <[hidden email]>:
> When I visit my Seaside 2.8 based app using a Palm Pre webOS phone the > initial page renders okay but when I click on any link I see only the > following. Any ideas? > > -Carl > > <html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml"> > <head> > <title>Error</title> > </head> > <body onkeydown="onKeyDown(event)" onload="onLoad()"> > <h3>Transport<http> failed - Wrong response status line: Origin : > http://irunbasic.com</h3> > </body> > </html> That's pretty interesting. I take it it runs on the iPhone? What I would recommend is doing a dump of the request and and the response with tcpdump. Cheers Philippe _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Hi Philippe,
Yes it works fine on the iPhone. I also do not have any trouble with another application written on Seaside 2.6 and 7.4.1. Oh yeah, I guess I forgot to mention that the troublesome Seaside 2.8 app is running on VW7.6. I still get the error if connect directly to the server on my local network instead of through my firewall and Apache, but without the all the XML from my original post. Transport failed - Wrong response status line: http://192.168.1.15 Here is text from tcpdump when the error occurs. Any idea what it means? -Carl 16:37:58.606460 IP 192.168.1.9.60081 > irunbasic.7070: Flags [P.], seq 2011:2627, ack 8964, win 889, options [nop,nop,TS val 8656850 ecr 128845041], length 616 16:37:58.606519 IP irunbasic.7070 > 192.168.1.9.60081: Flags [.], ack 2627, win 194, options [nop,nop,TS val 128847772 ecr 8656850], length 0 16:37:58.646366 IP irunbasic.7070 > 192.168.1.9.60081: Flags [P.], seq 8964:9228, ack 2627, win 194, options [nop,nop,TS val 128847782 ecr 8656850], length 264 16:37:58.648372 IP 192.168.1.9.60081 > irunbasic.7070: Flags [.], ack 9228, win 979, options [nop,nop,TS val 8656866 ecr 128847782], length 0 16:37:58.652090 IP 192.168.1.9.60081 > irunbasic.7070: Flags [P.], seq 2627:3217, ack 9228, win 979, options [nop,nop,TS val 8656866 ecr 128847782], length 590 16:37:58.652154 IP irunbasic.7070 > 192.168.1.9.60081: Flags [.], ack 3217, win 213, options [nop,nop,TS val 128847784 ecr 8656866], length 0 16:37:58.657222 IP irunbasic.7070 > 192.168.1.9.60081: Flags [P.], seq 9228:9555, ack 3217, win 213, options [nop,nop,TS val 128847785 ecr 8656866], length 327 16:37:58.672448 IP irunbasic.7070 > 192.168.1.9.60081: Flags [.], seq 9555:11003, ack 3217, win 213, options [nop,nop,TS val 128847789 ecr 8656866], length 1448 16:37:58.675018 IP 192.168.1.9.60081 > irunbasic.7070: Flags [.], ack 11003, win 1160, options [nop,nop,TS val 8656869 ecr 128847785], length 0 16:37:58.675084 IP irunbasic.7070 > 192.168.1.9.60081: Flags [P.], seq 11003:11050, ack 3217, win 213, options [nop,nop,TS val 128847790 ecr 8656869], length 47 16:37:58.684709 IP irunbasic.7070 > 192.168.1.9.60081: Flags [.], seq 11050:12498, ack 3217, win 213, options [nop,nop,TS val 128847792 ecr 8656869], length 1448 16:37:58.689873 IP irunbasic.7070 > 192.168.1.9.60081: Flags [.], seq 12498:13946, ack 3217, win 213, options [nop,nop,TS val 128847793 ecr 8656869], length 1448 16:37:58.703472 IP 192.168.1.9.60081 > irunbasic.7070: Flags [.], ack 12498, win 1251, options [nop,nop,TS val 8656872 ecr 128847790], length 0 16:37:58.703544 IP irunbasic.7070 > 192.168.1.9.60081: Flags [P.], seq 13946:14834, ack 3217, win 213, options [nop,nop,TS val 128847797 ecr 8656872], length 888 16:37:58.705490 IP 192.168.1.9.60081 > irunbasic.7070: Flags [.], ack 14834, win 1432, options [nop,nop,TS val 8656872 ecr 128847793], length 0 16:37:58.887350 STP 802.1d, Config, Flags [none], bridge-id ffff.ff:ff:90:28:96:85.8004, length 43 On Fri, Feb 11, 2011 at 1:01 AM, Philippe Marschall <[hidden email]> wrote: > 2011/2/11 Carl Gundel <[hidden email]>: >> When I visit my Seaside 2.8 based app using a Palm Pre webOS phone the >> initial page renders okay but when I click on any link I see only the >> following. Any ideas? >> >> -Carl >> >> <html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml"> >> <head> >> <title>Error</title> >> </head> >> <body onkeydown="onKeyDown(event)" onload="onLoad()"> >> <h3>Transport<http> failed - Wrong response status line: Origin : >> http://irunbasic.com</h3> >> </body> >> </html> > > That's pretty interesting. I take it it runs on the iPhone? What I > would recommend is doing a dump of the request and and the response > with tcpdump. > > Cheers > Philippe > _______________________________________________ > seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
2011/2/12 Carl Gundel <[hidden email]>:
> Hi Philippe, > > Yes it works fine on the iPhone. I also do not have any trouble with > another application written on Seaside 2.6 and 7.4.1. > > Oh yeah, I guess I forgot to mention that the troublesome Seaside 2.8 > app is running on VW7.6. > > I still get the error if connect directly to the server on my local > network instead of through my firewall and Apache, but without the all > the XML from my original post. > > Transport failed - Wrong response status line: http://192.168.1.15 > > Here is text from tcpdump when the error occurs. Any idea what it means? Can you dump the whole packets with -s 0 and write it to a file with -w ? Cheers Philippe _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Okay, here it is, attached.
Thanks, -Carl On Sun, Feb 13, 2011 at 6:48 AM, Philippe Marschall <[hidden email]> wrote: > 2011/2/12 Carl Gundel <[hidden email]>: >> Hi Philippe, >> >> Yes it works fine on the iPhone. I also do not have any trouble with >> another application written on Seaside 2.6 and 7.4.1. >> >> Oh yeah, I guess I forgot to mention that the troublesome Seaside 2.8 >> app is running on VW7.6. >> >> I still get the error if connect directly to the server on my local >> network instead of through my firewall and Apache, but without the all >> the XML from my original post. >> >> Transport failed - Wrong response status line: http://192.168.1.15 >> >> Here is text from tcpdump when the error occurs. Any idea what it means? > > Can you dump the whole packets with -s 0 and write it to a file with -w ? > > Cheers > Philippe > _______________________________________________ > seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside tcpdump.txt (20K) Download Attachment |
2011/2/14 Carl Gundel <[hidden email]>:
> Okay, here it is, attached. Thanks, that's very interesting. To me it looks like as if your Smalltalk image is generating this error message. First I thought it was the phone having trouble with the response. At that point it looks as if you have to debug Opentalk. For example search for strings containing 'Wrong response status line' and set a breakpoint there. Cheers Philippe _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Thanks. Looks like a problem in Net.HttpParser. Here is the code for
whoever is curious. I'll try the debugger on this when I get my hands on the server later. Thanks again, -Carl Net.HttpParser>>startMessageFrom: aStream | scanner fLine rfc822Scanner aString | aStream text. rfc822Scanner := self scannerOn: aStream. aString := rfc822Scanner nextLine. aString isEmpty ifTrue: [^HttpStatusLineError new messageText: (#EmptyHttpResponseStatusLine << #net >> 'Can not read external stream, returns empty the Http response status line') asString; raiseSignal]. scanner := self scannerOn: aString readStream. fLine := ('http' match: scanner nextToken asLowercase) ifTrue: [HttpResponseStatusLine readFrom: aString readStream] ifFalse: [HttpRequestLine readFrom: aString readStream ]. (fLine isNil or: [ fLine isValid not ]) ifTrue: [ ^HttpEntityError new messageText: ((#WrongResponseStatusLine << #net >> 'Wrong response status line: <1s>') expandMacrosWith: fLine printString); raiseSignal ]. ^self handler startMessage: fLine. On Mon, Feb 14, 2011 at 1:17 AM, Philippe Marschall <[hidden email]> wrote: > 2011/2/14 Carl Gundel <[hidden email]>: >> Okay, here it is, attached. > > Thanks, that's very interesting. To me it looks like as if your > Smalltalk image is generating this error message. First I thought it > was the phone having trouble with the response. At that point it looks > as if you have to debug Opentalk. For example search for strings > containing 'Wrong response status line' and set a breakpoint there. > > Cheers > Philippe seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Free forum by Nabble | Edit this page |