Hi list,
because of getting arbitrary 502 errors, i found out that the reason for that problem is an error in parsing the HTTPRequestLine. When it is not possible to find a corresponding HTTPRequest class is the leading character of the method a <lf>. I simple solved this problem by an additional #trimBlanks. Is this is a bug in Swazoo or my Firefox? regards Andreas -- Psst! Geheimtipp: Online Games kostenlos spielen bei den GMX Free Games! http://games.entertainment.web.de/de/entertainment/games/free _______________________________________________ Aida mailing list [hidden email] http://lists.aidaweb.si/mailman/listinfo/aida |
Hi Andreas,
Andreas Petermann wrote: > because of getting arbitrary 502 errors, i found out that the reason for that problem is an error in parsing the HTTPRequestLine. When it is not possible to find a corresponding HTTPRequest class is the leading character of the method a <lf>. I simple solved this problem by an additional #trimBlanks. > Is this is a bug in Swazoo or my Firefox? I didn't have first request line parsing errors for ages so I'm really interested what is happening in your case. Can you spy a network and record, what is actually flowing on the wire? With Ethereal or similar spy/network monitor. That way we will find a cause most efficiently. Janko -- Janko Mivšek AIDA/Web Smalltalk Web Application Server http://www.aidaweb.si _______________________________________________ Aida mailing list [hidden email] http://lists.aidaweb.si/mailman/listinfo/aida |
Hi Janko,Hi Andreas, Andreas Petermann wrote:because of getting arbitrary 502 errors, i found out that the reason for that problem is an error in parsing the HTTPRequestLine. When it is not possible to find a corresponding HTTPRequest class is the leading character of the method a <lf>. I simple solved this problem by an additional #trimBlanks. Is this is a bug in Swazoo or my Firefox?I didn't have first request line parsing errors for ages so I'm really interested what is happening in your case. Can you spy a network and record, what is actually flowing on the wire? With Ethereal or similar spy/network monitor. That way we will find a cause most efficiently. i will do it and mail the result the next week. I am interested in that problem too. Andreas _______________________________________________ Aida mailing list [hidden email] http://lists.aidaweb.si/mailman/listinfo/aida |
> >> because of getting arbitrary 502 errors, i found out that the reason > for that problem is an error in parsing the HTTPRequestLine. When it is not > possible to find a corresponding HTTPRequest class is the leading character > of the method a <lf>. I simple solved this problem by an additional > #trimBlanks. > >> Is this is a bug in Swazoo or my Firefox? > >> > > > > I didn't have first request line parsing errors for ages so I'm really > > interested what is happening in your case. Can you spy a network and > > record, what is actually flowing on the wire? With Ethereal or similar > > spy/network monitor. That way we will find a cause most efficiently. > > > > i have spied out the network traffic with the result, that there is no failure. The requests are all ok. It seems, that POST requests are parsed two times. I get one correct POST request and then i get the same one again, but this time only a part of the post data. And on trying to get the request type occurs the error. I am not sure why this happens, perhaps why the post data seems not to be parsed? regards Andreas -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer _______________________________________________ Aida mailing list [hidden email] http://lists.aidaweb.si/mailman/listinfo/aida |
Hi Andreas,
Now I know what is a problem and it is patched (I cannot say solved:) in latest Swazoo 2.1. Namely POSTs are somehow not parsed completelly and it seems a byte or so sometimes stay unparsed. But parsed content is correct anyway. That's why I didn't go deeper (besides I didn't have time). Quick solution is simply to close connection after a post and that's in Swazoo 2.1 in method HTTPConnection produceResponseFor: . Because POSTs are relatively rare comparing to GETs I think such quick problem solution won't affect Swazoo performance in general. I hope this help a bit Janko Andreas Petermann wrote: >>>> because of getting arbitrary 502 errors, i found out that the reason >> for that problem is an error in parsing the HTTPRequestLine. When it is not >> possible to find a corresponding HTTPRequest class is the leading character >> of the method a <lf>. I simple solved this problem by an additional >> #trimBlanks. >>>> Is this is a bug in Swazoo or my Firefox? >>>> >>> I didn't have first request line parsing errors for ages so I'm really >>> interested what is happening in your case. Can you spy a network and >>> record, what is actually flowing on the wire? With Ethereal or similar >>> spy/network monitor. That way we will find a cause most efficiently. >>> >>> > Hi Janko, > > i have spied out the network traffic with the result, that there is no failure. The requests are all ok. It seems, that POST requests are parsed two times. I get one correct POST request and then i get the same one again, but this time only a part of the post data. And on trying to get the request type occurs the error. I am not sure why this happens, perhaps why the post data seems not to be parsed? > > regards > Andreas > -- Janko Mivšek AIDA/Web Smalltalk Web Application Server http://www.aidaweb.si _______________________________________________ Aida mailing list [hidden email] http://lists.aidaweb.si/mailman/listinfo/aida |
Hi Janko,Hi Andreas, Now I know what is a problem and it is patched (I cannot say solved:) in latest Swazoo 2.1. Namely POSTs are somehow not parsed completelly and it seems a byte or so sometimes stay unparsed. But parsed content is correct anyway. That's why I didn't go deeper (besides I didn't have time). Quick solution is simply to close connection after a post and that's in Swazoo 2.1 in method HTTPConnection produceResponseFor: . Because POSTs are relatively rare comparing to GETs I think such quick problem solution won't affect Swazoo performance in general. I hope this help a bit Janko Andreas Petermann wrote:because of getting arbitrary 502 errors, i found out that the reasonfor that problem is an error in parsing the HTTPRequestLine. When it is not possible to find a corresponding HTTPRequest class is the leading character of the method a <lf>. I simple solved this problem by an additional #trimBlanks.Is this is a bug in Swazoo or my Firefox?I didn't have first request line parsing errors for ages so I'm really interested what is happening in your case. Can you spy a network and record, what is actually flowing on the wire? With Ethereal or similar spy/network monitor. That way we will find a cause most efficiently.Hi Janko, i have spied out the network traffic with the result, that there is no failure. The requests are all ok. It seems, that POST requests are parsed two times. I get one correct POST request and then i get the same one again, but this time only a part of the post data. And on trying to get the request type occurs the error. I am not sure why this happens, perhaps why the post data seems not to be parsed? regards Andreas yes it helps me a lot. Thank you very much. Andreas _______________________________________________ Aida mailing list [hidden email] http://lists.aidaweb.si/mailman/listinfo/aida |
Free forum by Nabble | Edit this page |