From: Micah Cowan
But, since any specific transaction is unlikely to take such a long
time, the spread of the run is easily deduced by the start and end
times, and, in the unlikely event of multiple days, counting time
regressions.
And if the pages in books were all numbered 1, 2, 3, 4,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Steven M. Schweda wrote:
But, since any specific transaction is unlikely to take such a long
time, the spread of the run is easily deduced by the start and end
times, and, in the unlikely event of multiple days, counting time
regressions.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
There is little left to finish up for Wget 1.11. I've decided to leave
certain issues related to Content-Disposition until 1.12
(Content-Disposition support in Wget 1.11 will be considered
experimental). The few other remaining issues are awaiting
My usage is counter to your assumptions below. I run every hour to
connect to 1,000 instruments (1,500 in 12 months) dispersed over the
entire western US and Alaska. I append log messages for all runs from
a day to a single file. This is an important debugging tool for us.
We have mostly VSAT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jim Wright wrote:
My usage is counter to your assumptions below.[...]
A change as proposed here is very simple, but
would be VERY useful.
Okay. Guess I'm sold, then. :D
- --
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer...
Micah Cowan micah at cowan.name writes:
Jim Wright wrote:
My usage is counter to your assumptions below.[...]
A change as proposed here is very simple, but
would be VERY useful.
Okay. Guess I'm sold, then. :D
--
Micah J. Cowan
Programmer, musician, typesetting enthusiast,
Zitat von Micah Cowan [EMAIL PROTECTED]:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jochen Roderburg wrote:
And now, for a change, a case, that works now (better) ;-)
This is an example where a HEAD request gets a 500 Error response.
Wget default options again, but
Zitat von Micah Cowan [EMAIL PROTECTED]:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jochen Roderburg wrote:
(abbreviated:)
51% [= ] 157,962
5.37K/s in 3m 45s
Further examination of such cases showed that a Byte-Range
Zitat von Micah Cowan [EMAIL PROTECTED]:
The problem you pointed out that causes the failure to properly
timestamp when HEADs aren't issued seems, to my reading, to be simply
regressable for the fix. Mauro's fixes don't look as if they depend upon
that line being there, but I'm waiting for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jochen Roderburg wrote:
Zitat von Micah Cowan [EMAIL PROTECTED]:
The problem you pointed out that causes the failure to properly
timestamp when HEADs aren't issued seems, to my reading, to be simply
regressable for the fix. Mauro's fixes don't
Zitat von Micah Cowan [EMAIL PROTECTED]:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jochen Roderburg wrote:
Yes, this one is still open, and the other one that wget -c always starts
at 0
again.
Do you mean the (local 0) thing? That should have been fixed in
674cc935f7c8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jochen Roderburg wrote:
Zitat von Micah Cowan [EMAIL PROTECTED]:
Jochen Roderburg wrote:
Yes, this one is still open, and the other one that wget -c always starts
at 0
again.
Do you mean the (local 0) thing? That should have been fixed in
12 matches
Mail list logo