in reply to initial http response not complete

It is possible that you are getting 'Chunked' transfer encoding - probably the best way of dealing with this is to use the callbacks to the request as in the second example in lwpcook

Of course without knowing the actual source of the data it is difficult to know.

/J\

Replies are listed 'Best First'.
Re^2: initial http response not complete
by seaver (Pilgrim) on Sep 21, 2004 at 14:57 UTC
    The actual URL is:

    http://wos4.isiknowledge.com/CIW.cgi

    however you have to go to the 'web of science' through the front page to create a session id (which is maintained in a hidden field in all the forms)

    I'm using 'General Search' and the keywords 'Emergence AND Complexity' in the topic field. This should return about 600 results but my initial response only has 62.

    Thanks
    Sam

    _____UPDATE______

    Ok, two things:

    I discovered from the request header that:

    HTTP/1.1 200 OK Connection: close Date: Tue, 21 Sep 2004 15:14:31 GMT Pragma: no-cache Server: Apache/1.3.29 (Unix) mod_perl/1.29 Perl/v5.6.1 Content-Type: text/html Client-Date: Tue, 21 Sep 2004 15:14:35 GMT Client-Response-Num: 1 Client-Transfer-Encoding: chunked Content-Base: http://wos4.isiknowledge.com:80/
    Which tells me that the response is 'chunked'. What exactly does this mean? Because I do get a full page for a response.

    Also, I checked out some JavaScript:

    http://wos4.isiknowledge.com/DynamicNum.js

    Which seems to have stuff to do with loading, but nothing that forces a reload...

    or is that what Im looking for?

    Thanks
    Sam