Theoretically, a HTTP/1.0 server should accept an unknown content-length
if the connection is closed after the request.
Unfortunately, the response 411 Length Required, is only defined in
HTTP/1.1.
//Stefan
Am Dienstag, 07.10.03, um 01:12 Uhr (Europe/Berlin) schrieb Hrvoje
Niksic:
As I was
On Tue, 7 Oct 2003, Hrvoje Niksic wrote:
My first impulse was to bemoan Wget's antiquated HTTP code which doesn't
understand chunked transfer. But, coming to think of it, even if Wget
used HTTP/1.1, I don't see how a client can send chunked requests and
interoperate with HTTP/1.0 servers.
Zitat von Hrvoje Niksic [EMAIL PROTECTED]:
Jochen Roderburg [EMAIL PROTECTED] writes:
Zitat von Hrvoje Niksic [EMAIL PROTECTED]:
It's a feature. `-A zip' means `-A zip', not `-A zip,html'. Wget
downloads the HTML files only because it absolutely has to, in order
to recurse through
Hrvoje Niksic [EMAIL PROTECTED] writes:
As for the Polish translation, translations are normally handled
through the Translation Project. The TP robot is currently down, but
I assume it will be back up soon, and then we'll submit the POT file
and update the translations /en masse/.
It took
Dan Jacobson [EMAIL PROTECTED] writes:
-q and -S are incompatible and should perhaps produce errors and be
noted thus in the docs.
They seem to work as I'd expect -- `-q' tells Wget to print *nothing*,
and that's what happens. The output Wget would have generated does
contain HTTP headers,
Karl Eichwalder [EMAIL PROTECTED] writes:
Hrvoje Niksic [EMAIL PROTECTED] writes:
As for the Polish translation, translations are normally handled
through the Translation Project. The TP robot is currently down, but
I assume it will be back up soon, and then we'll submit the POT file
and
Karl Eichwalder [EMAIL PROTECTED] writes:
Also, my Croatian translation of 1.9 doesn't seem to have made it
in. Is that expected?
Unfortunately, yes. Will you please resubmit it with the subject line
updated (IIRC, it's now):
TP-Robot wget-1.9-b3.hr.po
I'm not sure what b3 is, but
Karl Eichwalder [EMAIL PROTECTED] writes:
Hrvoje Niksic [EMAIL PROTECTED] writes:
I'm not sure what b3 is, but the version in the POT file was
supposed to be beta3. Was there a misunderstanding somewhere along
the line?
Yes, the robot does not like beta3 as part of the version
string. b3
Karl Eichwalder [EMAIL PROTECTED] writes:
Hrvoje Niksic [EMAIL PROTECTED] writes:
Ouch. Why does the robot care about version names at all?
It must know about the sequences; this is important for merging
issues. IIRC, we have at least these sequences supported by the
robot:
1.2 -
Hrvoje Niksic wrote:
Please be aware that Wget needs to know the size of the POST data
in advance. Therefore the argument to @code{--post-file} must be
a regular file; specifying a FIFO or something like
@file{/dev/stdin} won't work.
There's nothing that says you have to
Tony Lewis [EMAIL PROTECTED] writes:
Hrvoje Niksic wrote:
Please be aware that Wget needs to know the size of the POST
data in advance. Therefore the argument to @code{--post-file}
must be a regular file; specifying a FIFO or something like
@file{/dev/stdin} won't work.
Am Dienstag, 07.10.03, um 16:36 Uhr (Europe/Berlin) schrieb Hrvoje
Niksic:
What the current code does is: determine the file size, send
Content-Length, read the file in chunks (up to the promised size) and
send those chunks to the server. But that works only with regular
files. It would be
Karl Eichwalder [EMAIL PROTECTED] writes:
I guess, you as the wget maintainer switched from something
supported to the unsupported betaX scheme and now we have
something to talk about ;)
I had no idea that something as usual as betaX was unsupported. In
fact, I believe that bX was added when
Stefan Eissing [EMAIL PROTECTED] writes:
Am Dienstag, 07.10.03, um 16:36 Uhr (Europe/Berlin) schrieb Hrvoje
Niksic:
What the current code does is: determine the file size, send
Content-Length, read the file in chunks (up to the promised size) and
send those chunks to the server. But that
Am Dienstag, 07.10.03, um 17:02 Uhr (Europe/Berlin) schrieb Hrvoje
Niksic:
That's probably true. But have you tried sending without
Content-Length and Connection: close and closing the output side of
the socket before starting to read the reply from the server?
That might work, but it sounds too
Hello Hrvoje and Dan,
I have been using wget for many years now, and finally got to applying
a patch I made long ago (EBCDIC patch against wget-1.5.3) to the
current wget-1.8.2. This patch makes wget compile and run on a
mainframe computer using the EBCDIC character set.
Also, when compiling
Martin, thanks for the patch and the detailed report. Note that it
might have made more sense to apply the patch to the latest CVS
version, which is somewhat different from 1.8.2.
I'm really not sure whether to add this patch. On the one hand, it's
nice to support as many architectures as
Hello,
I have noticed very unpredictable behavior from wget 1.8.2 - specifically
I have noticed two things:
a) sometimes it does not follow all of the links it should
b) sometimes wget will follow links to other sites and URLs - when the
command line used should not allow it to do that.
Here
Hrvoje Niksic wrote:
I don't understand what you're proposing. Reading the whole file in
memory is too memory-intensive for large files (one could presumably
POST really huge files, CD images or whatever).
I was proposing that you read the file to determine the length, but that was
on the
Tony Lewis [EMAIL PROTECTED] writes:
Hrvoje Niksic wrote:
I don't understand what you're proposing. Reading the whole file in
memory is too memory-intensive for large files (one could presumably
POST really huge files, CD images or whatever).
I was proposing that you read the file to
Josh Brooks [EMAIL PROTECTED] writes:
I have noticed very unpredictable behavior from wget 1.8.2 -
specifically I have noticed two things:
a) sometimes it does not follow all of the links it should
b) sometimes wget will follow links to other sites and URLs - when the
command line used
Thank you for the great response. It is much appreciated - see below...
On Tue, 7 Oct 2003, Hrvoje Niksic wrote:
www.zorg.org/vsound/ contains this markup:
META NAME=ROBOTSCONTENT=NOFOLLOW
That explicitly tells robots, such as Wget, not to follow the links in
the page. Wget
Hrvoje Niksic wrote:
That would work for short streaming, but would be pretty bad in the
mkisofs example. One would expect Wget to be able to stream the data
to the server, and that's just not possible if the size needs to be
known in advance, which HTTP/1.0 requires.
One might expect it,
Thanks everyone for the replies so far..
The problem I am having is that the customer is using ASP Java script. The URL stays
the same as I click through the links. So, using wget URL for the page I want may
not work (I may be wrong). Any suggestions on how I can tackle this?
Thanks,
Suhas Tembe [EMAIL PROTECTED] writes:
Thanks everyone for the replies so far..
The problem I am having is that the customer is using ASP Java
script. The URL stays the same as I click through the links.
URL staying the same is usually a sign of the use of frame, not of ASP
and
Got it! Thanks! So far so good. After logging-in, I was able to get to the page I am
interested in. There was one thing that I forgot to mention in my earlier posts (I
apologize)... this page contains a drop-down list of our customer's locations. At
present, I choose one location from the
Suhas Tembe [EMAIL PROTECTED] writes:
this page contains a drop-down list of our customer's locations.
At present, I choose one location from the drop-down list click
submit to get the data, which is displayed in a report format. I
right-click then choose view source save source to a file.
It does look a little complicated This is how it looks:
form action=InventoryStatus.asp method=post name=select onsubmit=return
select_validate(); style=margin:0
div style=margin-top:10px
table border=1 bordercolor=#d9d9d9 bordercolordark=#ff
bordercolorlight=#d9d9d9 cellpadding=3
Suhas Tembe [EMAIL PROTECTED] writes:
It does look a little complicated This is how it looks:
form action=InventoryStatus.asp method=post [...]
[...]
select name=cboSupplier
option value=4541-134289454A/option
option value=4542-134289 selected454B/option
/select
Those are the
29 matches
Mail list logo
