"H. Chaudet" wrote:
>
> Just two questions:
> - Is the httpheaders property definitively obsolete and replaced by "set
> the {getHeader1 | postheader} of stack libURL to ..." ?
For now, yes, though I'm planing to make it work: it will just add
header lines to the existing ones.
Until then do what you say above.
> - Does this means that the libURL stack must be attached to a standalone stack?
Yes, though you could just copy/adapt the relevant parts.
>
>
> What is strange about this behavior is that I have no problem with MC 2.3
> (the most puzzling), Netscape, or IE.
The reason is that MC 2.3 sends HTTP/1.0 which tells the server to
respond the simple way (no "chunked" data) and same does Netscape. I
guess you could change HTTP/1.1 to HTTP/1.0 in the header, see what
happens.
>
> Herve
>
Andu
Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
