Restlet and FF in Windows: range out of range

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Restlet and FF in Windows: range out of range

Diego Ballve
Hello,

Can somebody take a look at the range headers in these greps? I'm
experiencing problems in Windows when serving static files (times out
most of the times) and I believe it's due to ranged requests since it
works fine linux (1 request).

More specifically, why does Restlet answer:
  Content-Range: bytes 262144-728134/465990..
when
  Content-Length: 465990..

Thanks,
Diego

LINUX:
T 127.0.0.1:45659 -> 127.0.0.1:8183 [AP]
  GET /app/out.pdf HTTP/1.1..
  Host: 127.0.0.1:8183..
  User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.3)
Gecko/2008092416 Firefox/3.0.3..
  Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8..
  Accept-Language: en,en-us;q=0.7,fi;q=0.3..
  Accept-Encoding: gzip,deflate..
  Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7..
  Keep-Alive: 300..
  Connection: keep-alive....
##
T 127.0.0.1:8183 -> 127.0.0.1:45659 [AP]
  HTTP/1.1 200 The request has succeeded..
  Expires: Thu, 30 Oct 2008 19:19:38 GMT..
  Content-Language: en-us..
  Content-Type: application/pdf..
  Last-Modified: Wed, 29 Oct 2008 14:36:31 GMT..
  Content-Length: 465990..
  Content-Location: http://127.0.0.1:8183/app//out.pdf..
  Date: Thu, 30 Oct 2008 19:09:38 GMT..
  Vary: Accept-Charset, Accept-Encoding, Accept-Language, Accept..
  Accept-Ranges: bytes..
  Cache-Control: no-cache..
  Pragma: no-cache..
  Server: Noelios-Restlet-Engine/1.1.rc2..
  Connection: close....

WINDOWS:
T 127.0.0.1:45666 -> 127.0.0.1:8183 [AP]
  GET /app/out.pdf HTTP/1.1..
  Host: 127.0.0.1:8183..
  User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3..
  Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8..
  Accept-Language: en-us,en;q=0.5..
  Accept-Encoding: gzip,deflate..
  Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7..
  Keep-Alive: 300..
  Connection: keep-alive..
  Range: bytes=262144-..
  If-Range: Wed, 29 Oct 2008 14:36:31 GMT....
##
T 127.0.0.1:8183 -> 127.0.0.1:45666 [AP]
  HTTP/1.1 206 The server has fulfilled the partial get request for the
resource..
  Expires: Thu, 30 Oct 2008 19:21:23 GMT..
  Content-Language: en-us..
  Content-Type: application/pdf..
  Last-Modified: Wed, 29 Oct 2008 14:36:31 GMT..
  Content-Length: 465990..
  Content-Location: http://127.0.0.1:8183/app//out.pdf..
  Content-Range: bytes 262144-728134/465990..
  Date: Thu, 30 Oct 2008 19:11:23 GMT..
  Vary: Accept-Charset, Accept-Encoding, Accept-Language, Accept..
  Accept-Ranges: bytes..
  Cache-Control: no-cache..
  Pragma: no-cache..
  Server: Noelios-Restlet-Engine/1.1.rc2..
  Connection: close....

T 127.0.0.1:45667 -> 127.0.0.1:8183 [AP]
  GET /app/out.pdf HTTP/1.1..
  Host: 127.0.0.1:8183..
  User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3..
  Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8..
  Accept-Language: en-us,en;q=0.5..
  Accept-Encoding: gzip,deflate..
  Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7..
  Keep-Alive: 300..
  Connection: keep-alive..
  Range: bytes=172032-465989,172032-172033....
##
T 127.0.0.1:8183 -> 127.0.0.1:45667 [AP]
  HTTP/1.1 416 For byte ranges, this means that the first byte position
were greater than the current length of the selected resource..
  Content-Type: text/html; charset=ISO-8859-1..
  Content-Length: 1174..
  Date: Thu, 30 Oct 2008 19:11:23 GMT..
  Vary: Accept-Charset, Accept-Encoding, Accept-Language, Accept..
  Accept-Ranges: bytes..
  Cache-Control: no-cache..
  Pragma: no-cache..
  Server: Noelios-Restlet-Engine/1.1.rc2..
  Connection: close....
##
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Restlet and FF in Windows: range out of range

Rob Heittman
This may be connected to a recent issue I've seen with Acrobat 9 not being able to serve up certain PDFs hosted by Restlet -- there are also ranged requests going on there -- Jerome and Thierry contact me direct if you want examples.

- Rob

On Fri, Oct 31, 2008 at 11:18 AM, Diego Ballve <[hidden email]> wrote:
Hello,

Can somebody take a look at the range headers in these greps? I'm
experiencing problems in Windows when serving static files (times out
most of the times) and I believe it's due to ranged requests since it
works fine linux (1 request).

More specifically, why does Restlet answer:
 Content-Range: bytes 262144-728134/465990..
when
 Content-Length: 465990..

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: Restlet and FF in Windows: range out of range

jlouvel
Administrator
Hi all,
 
I've entered a bug report for this:
 
"Fix issues with content ranges"
 
Diego, could you specify which connectors you are using as this way have an impact?
 
A workaround is to turn off content ranges in your application: getRangeService().setEnabled(false);
 
Best regards,
Jérôme Louvel
--
Restlet ~ Founder and Lead developer ~
http://www.restlet.org
Noelios Technologies ~ Co-founder ~ http://www.noelios.com


De : Rob Heittman [mailto:[hidden email]]
Envoyé : vendredi 31 octobre 2008 16:28
À : [hidden email]
Objet : Re: Restlet and FF in Windows: range out of range

This may be connected to a recent issue I've seen with Acrobat 9 not being able to serve up certain PDFs hosted by Restlet -- there are also ranged requests going on there -- Jerome and Thierry contact me direct if you want examples.

- Rob

On Fri, Oct 31, 2008 at 11:18 AM, Diego Ballve <[hidden email]> wrote:
Hello,

Can somebody take a look at the range headers in these greps? I'm
experiencing problems in Windows when serving static files (times out
most of the times) and I believe it's due to ranged requests since it
works fine linux (1 request).

More specifically, why does Restlet answer:
 Content-Range: bytes 262144-728134/465990..
when
 Content-Length: 465990..

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Restlet and FF in Windows: range out of range

Diego Ballve
Hello,

Thanks for the workaround hint. We're using the default NRE connectors,
only HTTP for server.

We actually have it running behind apache proxy, so we could do set
these in the <proxy> session in apache, once we narrowed down the problem:
      RequestHeader unset "Range"
      RequestHeader unset "If-Range"

Regards,
Diego

Jerome Louvel wrote:

> Hi all,
>  
> I've entered a bug report for this:
>  
> "Fix issues with content ranges"
> http://restlet.tigris.org/issues/show_bug.cgi?id=642
>  
> Diego, could you specify which connectors you are using as this way have
> an impact?
>  
> A workaround is to turn off content ranges in your application:
> getRangeService().setEnabled(false);
>  
> Best regards,
> Jérôme Louvel
> --
> Restlet ~ Founder and Lead developer ~ http://www.restlet.org
> <http://www.restlet.org/>
> Noelios Technologies ~ Co-founder ~ http://www.noelios.com
> <http://www.noelios.com/>
>
> ------------------------------------------------------------------------
> *De :* Rob Heittman [mailto:[hidden email]]
> *Envoyé :* vendredi 31 octobre 2008 16:28
> *À :* [hidden email]
> *Objet :* Re: Restlet and FF in Windows: range out of range
>
> This may be connected to a recent issue I've seen with Acrobat 9 not
> being able to serve up certain PDFs hosted by Restlet -- there are also
> ranged requests going on there -- Jerome and Thierry contact me direct
> if you want examples.
>
> - Rob
>
> On Fri, Oct 31, 2008 at 11:18 AM, Diego Ballve
> <[hidden email]
> <mailto:[hidden email]>> wrote:
>
>     Hello,
>
>     Can somebody take a look at the range headers in these greps? I'm
>     experiencing problems in Windows when serving static files (times out
>     most of the times) and I believe it's due to ranged requests since it
>     works fine linux (1 request).
>
>     More specifically, why does Restlet answer:
>      Content-Range: bytes 262144-728134/465990..
>     when
>      Content-Length: 465990..
>
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Restlet and FF in Windows: range out of range

Thierry Boileau
Hello Diego,


thanks to your report, some issues regarding the support of ranges have been adressed (calculation of the content-length header, and
in some cases the calculation of the content-range header). The behavior under certain circumstances have been clarified: when the length of the entity is
unknown and the client requests the last bytes, this is very difficult to compute the absolute indexes as required in the "content-range" header. Thus, it
has been decided to simply return an internal server error (status 500).
Having said that, we still need the support of multiple ranges (see http://restlet.tigris.org/issues/show_bug.cgi?id=651) based on the incoming support of multipart entities.

Best regards,
Thierry Boileau
--
Restlet ~ Core developer ~ http://www.restlet.org
Noelios Technologies ~ Co-founder ~ http://www.noelios.com


Hello,

Thanks for the workaround hint. We're using the default NRE connectors,
only HTTP for server.

We actually have it running behind apache proxy, so we could do set
these in the <proxy> session in apache, once we narrowed down the problem:
      RequestHeader unset "Range"
      RequestHeader unset "If-Range"

Regards,
Diego

Jerome Louvel wrote:
  
Hi all,
 
I've entered a bug report for this:
 
"Fix issues with content ranges"
http://restlet.tigris.org/issues/show_bug.cgi?id=642
 
Diego, could you specify which connectors you are using as this way have
an impact?
 
A workaround is to turn off content ranges in your application:
getRangeService().setEnabled(false);
 
Best regards,
Jérôme Louvel
--
Restlet ~ Founder and Lead developer ~ http://www.restlet.org
<http://www.restlet.org/>
Noelios Technologies ~ Co-founder ~ http://www.noelios.com
<http://www.noelios.com/>

------------------------------------------------------------------------
*De :* Rob Heittman [[hidden email]]
*Envoyé :* vendredi 31 octobre 2008 16:28
*À :* [hidden email]
*Objet :* Re: Restlet and FF in Windows: range out of range

This may be connected to a recent issue I've seen with Acrobat 9 not
being able to serve up certain PDFs hosted by Restlet -- there are also
ranged requests going on there -- Jerome and Thierry contact me direct
if you want examples.

- Rob

On Fri, Oct 31, 2008 at 11:18 AM, Diego Ballve
<[hidden email]
[hidden email]> wrote:

    Hello,

    Can somebody take a look at the range headers in these greps? I'm
    experiencing problems in Windows when serving static files (times out
    most of the times) and I believe it's due to ranged requests since it
    works fine linux (1 request).

    More specifically, why does Restlet answer:
     Content-Range: bytes 262144-728134/465990..
    when
     Content-Length: 465990..

    
Loading...