Re: [Winstone-devel] http 1.1 range-header

[Paul v. L. (Collis) <le...@co...>]

Hi Rick,

Again you have helped me a lot. Thank you for your time. I have contacted Hudson and will try to work it out with them. Many thanks!

Regards,
Paul

-----Original Message-----
From: Rick Knowles [mailto:ri...@kn...] 
Sent: donderdag 8 oktober 2009 12:59
To: Paul van Leeuwen (Collis)
Cc: win...@li...
Subject: Re: [Winstone-devel] http 1.1 range-header

No - a servlet container is by definition an http server.

The servlet running inside the container is responsible for interpreting 
the HTTP headers beyond what is required for servlet spec compliance. 
Range headers are outside of the servlet spec.

Hudson has servlets that respond to your browser clicks / URL accesses. 
Once winstone has parsed and forwarded requests to the correct servlet, 
it delegates almost completely to that servlet for response generation - 
so you need to talk to someone from the Hudson team who wrote the 
servlets and ask them to support 206 response codes.

You can (and probably should if you experience any problems with a 
winstone environment) run hudson on top of tomcat, weblogic, resin or 
any servlet container you like. I doubt this will fix your problem 
though, unless they know something I don't .... not altogether impossible :)

Hope that helps,

Rick

Paul van Leeuwen (Collis) wrote:
> Thank you for your response Rick. (As far as my knowledge goes, I try to phrase this next question correctly:) If Winstone is 'just' a servlet container, does that mean that Hudson has a separate webserver thing, that only _uses_ Winstone, but the actual serving is done not by Winstone? What component is responsible for supporting ranges and what component generates those http headers? Or is this a question I would have to ask the Hudson team?
>
> Regards,
> Paul
>
> -----Original Message-----
> From: Rick Knowles [mailto:ri...@kn...] 
> Sent: donderdag 8 oktober 2009 8:32
> To: Paul van Leeuwen (Collis)
> Cc: win...@li...
> Subject: Re: [Winstone-devel] http 1.1 range-header
>
> Might want to take that up with Kawaguchi-san ... the servlet itself is 
> responsible for range processing, not the container. Winstone implements 
> it on static resources, but for custom servlets there's no conceivable 
> way this could be done without violating the servlet spec.
>
> Hope that helps,
>
> Rick
>
> Paul van Leeuwen (Collis) wrote:
>   
>> Dear mister Knowles,
>>
>> When sending a HTTP GET request to Hudson, requesting a specific 
>> range, then Winstone does not return that range, but returns the whole 
>> file (this is visible in the below screenshot).
>>
>> According to the http specification this is allowed: 
>> http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.35.2
>>
>> Quote: "A server MAY ignore the Range header. However, HTTP/1.1 origin 
>> servers and intermediate caches ought to support byte ranges when 
>> possible, since Range supports efficient recovery from partially 
>> failed transfers, and supports efficient partial retrieval of large 
>> entities."
>>
>> Does Winstone really not support ranges, or is this something that is 
>> configurable in some way? If not configurable, is there a newer 
>> version (we have Winstone/0.9.10) that does support ranges?
>>
>> Thank you for your time!
>>
>> Regards,
>>
>> Paul
>>
>>