Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[orion-dev] help with missing Content-Length in header returned for built-index.js

Hi,

I wonder if anyone can help.  We have a system that is processing the
responses from orion (kind of like a proxy), it is having trouble
because the built-index.js file is not returning a Content-Length in
its header response.  Other files do:

curl -v --http1.0 --header "Accept-Encoding: gzip, deflate"
http://orion.eclipse.org/plugin.js 2>&1 > foo.out | grep Content
< Content-Type: text/html;charset=ISO-8859-1
< Content-Encoding: gzip
< Content-Length: 269

But not built-index.js:

curl -v --http1.0 --header "Accept-Encoding: gzip, deflate"
http://orion.eclipse.org/built-index.js 2>&1 > foo.out | grep Content
< Content-Type: application/x-javascript
< Content-Encoding: gzip

Running that second command against a local configuration includes an
extra bit of info:

curl -v --http1.0 --header "Accept-Encoding: gzip, deflate"
http://localhost:8085/built-index.js > foo.out
....
* no chunk, no close, no size. Assume close to signal end
....

I see that built-index.js is a 500k file.  The smaller jslintworker.js
(200k) also exhibits this behaviour.  The files down around 50k are
fine (e.g. searchExplorer.js)

Does anyone know why this is? Is it feasible to ensure a
Content-Length is always returned even for these large files?  Is it a
jetty config option?

many thanks
Andy


Back to the top