If you do not provide content-length 1 of 2 things will happen.
1. Download will not show progress, only barber pole, and will not
always work on some clients.
2. Some clients, and I believe IE 6 was one, will just not download at
all.
If the content length is not accurate, it will many times result in
corrupted download, or a download that never ends, like if content-
length is 1 byte more than actual.
This issue occurs when using <@length to determine byte length on
binary data. I have seen it also occur on jpegs. When eventpix was
using this method, we had to go to storing bytelength in db, and not
relying on @length, because 1 out of every 1000 images or so would not
display due to this.
I am pulling from my memory, but this was a major issue for us with
both JPEGs and PDF libraries and was completely researched.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/
On May 9, 2008, at 12:45 PM, Kent Swisher wrote:
My intuition says they may be related.
Problem 1: Witango provides wrong LENGTH value with some files.
Problem 2: When content-length is off by 1 byte, some browsers will
have problems. What kind of problems was not stated.
Robert said on rare cases when happened, it was specific to a file.
Robert - Did this problem only happen with PDFs or other file types
too? When you have the problem, did the file download successfully
but not open via browser, or could not get to open in windows at all?
Bill - With these MacOS9 uploaded PDFs, did Witango provide the
wrong LENGTH value? Would they just not open via the browser, or
could not be opened at all in windows?
--
--> Kent Swisher Engineering Tools
--> Alcatel-Lucent Application Support Engineer
--> Wireline Access Products [EMAIL PROTECTED]
--> Petaluma, CA 707-792-7116 (on net 2-855-7116)
On 5/9/2008 10:10 AM, Robert Garcia wrote:
That makes sense, but that wasn't the issue I saw. This was a huge
pdf library, loaded into db myself from disk. When witango did the
length of the data retrieved from db, sometimes off, rare, but it
happens. Also, it would happen on the same pdf over and over, and
none of the others. When using binary length function from mysql,
no issues. Or, when populating the database with a LENGTH value,
calculating from RB on the way, no issue. The difference was
usually 1 byte.
On May 9, 2008, at 9:38 AM, William M Conlon wrote:
> This issue I experienced was that pdf files would not open in
windows. > It turned out that the pdf downloaded to windows was one
byte longer
> than the pdf uploaded from MacOS9. When I did a side-by-side
> comparison (pdfs are readable in a text editor even though there are
> non-printing characters) there was an extra line terminator (I
> forget which one).
>
> Bill
>
> William M. Conlon, P.E., Ph.D.
> To the Point
> 2330 Bryant Street
> Palo Alto, CA 94301
> vox: 650.327.2175 (direct)
> fax: 650.329.8335
> mobile: 650.906.9929
> e-mail: mailto:[EMAIL PROTECTED]
> web: http://www.tothept.com
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
