> What kind of extra data is it the server sends; random bytes, blank > lines, or what?
Here is an exemplary TCP stream-dump: ---------------------------------------------- GET / HTTP/1.1 Host: depatisnet.dpma.de Keep-Alive: Connection: TE, Keep-Alive TE: trailers User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.8) Gecko/20051215 Firefox/1.5 Accept: */* HTTP/1.1 302 Moved Temporarily Date: Fri, 23 Jun 2006 15:17:59 GMT Server: Oracle-Application-Server-10g/10.1.2.0.0 Oracle-HTTP-Server OracleAS-Web-Cache-10g/10.1.2.0.0 (N;ecid=835104371219,0) Cache-Control: private Location: http://depatisnet.dpma.de:80/DepatisNet/depatisnet?window=1&space=unknown&content=index&action=index&session=c23b66f2cea7587e8d32c534595a391a1cc23286edf&stamp=51910 Content-Type: text/html Set-Cookie: JSESSIONID=c23b66f2cea7587e8d32c534595a391a1cc23286edf.e34Pa3uOcheTaO0ObN8Nc3aSa390n6jAmljGr5XDqQLvpAe; path=/DepatisNet Set-Cookie: lang=de; path=/ Content-Length: 573 Content-Location: http://dn-appcl.depatis.dpma.de:3306/DepatisNet/depatisnet2 <HTML><HEAD><TITLE>Redirect to http://depatisnet.dpma.de:80/DepatisNet/depatisnet?window=1&space=unknown&content=index&action=index&session=c23b66f2cea7587e8d32c534595a391a1cc23286edf&stamp=51910</TITLE></HEAD><BODY><A HREF="http://depatisnet.dpma.de:80/DepatisNet/depatisnet?window=1&space=unknown&content=index&action=index&session=c23b66f2cea7587e8d32c534595a391a1cc23286edf&stamp=51910";>http://depatisnet.dpma.de:80/DepatisNet/depatisnet?window=1&space=unknown&content=index&action=index&session=c23b66f2cea7587e8d32c534595a391a1cc23286edf&stamp=51910</A></BODY></HTML><!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Moved Temporarily</title> </head><body> <h1>Moved Temporarily</h1> <p>The document has moved <a href="http://depatisnet.dpma.de:80/DepatisNet/depatisnet?window=1&space=unknown&content=index&action=index&session=c23b66f2cea7587e8d32c534595a391a1cc23286edf&stamp=51910";>here</a>.</p> </body></html> ------------------------------------------------------------------------- The internal socket buffer-position, that neon reads, when it expects the beginning of the next HTTP response is "<!DOCTYPE...", after exactly 573 bytes oft HTTP data of the shown response. Thank you for your suggestions by the way, will have a look at that later. For now I extended my copy of neon by a function, that explicitly purges the socket buffer through multiple calls to ne_socket_read... Regards, Thomas _______________________________________________ neon mailing list [email protected] http://mailman.webdav.org/mailman/listinfo/neon
