Dan Jacobson <[EMAIL PROTECTED]> writes:
> The documents don't say how or why one can/not force wget to send
> HTTP 1.1 headers, instead of 1.0. Maybe it is simply not ready yet?
It's not. The missing piece is the "chunked" transfer mode.
The documents don't say how or why one can/not force wget to send
HTTP 1.1 headers, instead of 1.0. Maybe it is simply not ready yet?
On Sunday 02 June 2002 09:38 am, Hack Kampbjørn wrote:
> Mark Bucciarelli wrote:
> > I am having trouble wgetting a samsung printer driver from their site.
> > Every time I try, I immediately get an HTTP/1.1 500 Internal Server
> > Error. The web browser initiates the dow
Hack Kampbjørn <[EMAIL PROTECTED]> writes:
> But I'm not sure wget should do [HTML de-quoting] for URLs on the
> cmd line or in a non-HTML file.
I'm pretty sure that it shouldn't. HTML unquoting only makes sense in
the context of HTML. That's how the browsers behave, as well --
typing "&" in t
Mark Bucciarelli wrote:
>
> I am having trouble wgetting a samsung printer driver from their site. Every
> time I try, I immediately get an HTTP/1.1 500 Internal Server Error. The
> web browser initiates the download properly when I click on the link from the
> referer page.
&
I am having trouble wgetting a samsung printer driver from their site. Every
time I try, I immediately get an HTTP/1.1 500 Internal Server Error. The
web browser initiates the download properly when I click on the link from the
referer page.
Here is the command I am running (I don't h
here
won't be any problems. If there any alternative libraries handling HTTP 1.1
references that would be better to use, please let me know.
Aloha,
RK.
You did something because it had always been done, and the explanation was,
"but we've always done it this way." A million dea
[EMAIL PROTECTED] writes:
>>Csaba Raduly's patch would break Wget because it doesn't suppose the
>>"chunked" transfer-encoding. Also, its understanding of persistent
>>connection might not be compliant with HTTP/1.1.
>
> IT WAS A JOKE !
I know that.
On 12/04/2002 21:37:31 hniksic wrote:
>"Tony Lewis" <[EMAIL PROTECTED]> writes:
>
>> Hrvoje Niksic wrote:
>>
>>> > Is there any way to make Wget use HTTP/1.1 ?
>>>
>>> Unfortunately, no.
>>
>> In looking at the debug o
"Tony Lewis" <[EMAIL PROTECTED]> writes:
> Hrvoje Niksic wrote:
>
>> > Is there any way to make Wget use HTTP/1.1 ?
>>
>> Unfortunately, no.
>
> In looking at the debug output, it appears to me that wget is really
> sending HTTP/1.1 headers
On 12 Apr 2002 at 11:59, Tony Lewis wrote:
> Hrvoje Niksic wrote:
>
> > > Is there any way to make Wget use HTTP/1.1 ?
> >
> > Unfortunately, no.
>
> In looking at the debug output, it appears to me that wget is really sending
> HTTP/1.1 headers, but cla
On 12 Apr 2002 at 21:41, Boaz Yahav wrote:
> So basically I only need to make this change and recompile?
> I wish this was a switch :)
No, it just lies to the server. Wget is not really an HTTP/1.1
client and may go up in smoke if the server thinks it is!
(Hopefully it contains
Hrvoje Niksic wrote:
> > Is there any way to make Wget use HTTP/1.1 ?
>
> Unfortunately, no.
In looking at the debug output, it appears to me that wget is really sending
HTTP/1.1 headers, but claiming that they are HTTP/1.0 headers. For example,
the Host header was not defined in R
So basically I only need to make this change and recompile?
I wish this was a switch :)
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 12, 2002 12:58 PM
Cc: Boaz Yahav; [EMAIL PROTECTED]
Subject: Re: HTTP 1.1
On 11/04/2002 18:26:15 hniksic
On 11/04/2002 18:26:15 hniksic wrote:
>"Boaz Yahav" <[EMAIL PROTECTED]> writes:
>
>> Is there any way to make Wget use HTTP/1.1 ?
>
>Unfortunately, no.
Sure it can be made to use HTTP 1.1
--- http.c.orig Wed Jan 30 14:10:42 2002
+++ http.c Fri Apr
"Boaz Yahav" <[EMAIL PROTECTED]> writes:
> Is there any way to make Wget use HTTP/1.1 ?
Unfortunately, no.
Hi
Is there any way to make Wget
use HTTP/1.1 ?
Thanks
berber
On 1 Feb 2002 at 8:17, Daniel Stenberg wrote:
> You may count this mail as advocating for HTTP 1.1 support, yes! ;-)
I did write down some minimal requirements for HTTP/1.1 support on
a scrap of paper recently. It's probably still buried under the
more recent strata of crap on my desk s
18 matches
Mail list logo