2:47 p.m.
Hello,
with all versions I tried (including 1.2.0.Beta9) undertow-core will
return content-length: 0 if a HEAD request is made.
I am using a simple handler:
FileResourceManager frm = new FileResourceManager(new
File(".").getCanonicalFile(), 16*1024);
ResourceHandler res = new ResourceHandler();
res.setResourceManager(frm);
res.setAllowed(Predicates.truePredicate());
res.setDirectoryListingEnabled(true);
PathHandler path = Handlers.path(errorHandler);
path.addPrefixPath("/res", res);
GracefulShutdownHandler shutdownHandler = Handlers.gracefulShutdown(path);
Undertow server = Undertow.builder().addHttpListener(8080, null)
.setServerOption(UndertowOptions.RECORD_REQUEST_START_TIME,
Boolean.TRUE)
.setServerOption(UndertowOptions.ALWAYS_SET_DATE, Boolean.TRUE) //
default
.setWorkerThreads(2).setHandler(shutdownHandler).build();
server.start();
If I request the GET method the content is found:
curl -v http://localhost:8080/webdav/pom.xml
* Connected to localhost (127.0.0.1) port 8080 (#0)
GET /res/pom.xml HTTP/1.1
User-Agent: curl/7.30.0
Host: localhost:8080
Accept: */*
< HTTP/1.1 200 OK
< Connection: keep-alive
< Last-Modified: Fri, 13 Mar 2015 19:24:58 GMT
< Content-Length: 1155
< Content-Type: text/xml
< Date: Fri, 13 Mar 2015 19:39:24 GMT
<
...
curl -v -XHEAD http://localhost:8080/webdav/pom.xml
* Connected to localhost (127.0.0.1) port 8080 (#0)
HEAD /webdav/pom.xml HTTP/1.1
User-Agent: curl/7.30.0
Host: localhost:8080
Accept: */*
< HTTP/1.1 200 OK
< Connection: keep-alive
< Last-Modified: Fri, 13 Mar 2015 19:24:58 GMT
< Content-Length: 0
< Content-Type: text/xml
< Date: Fri, 13 Mar 2015 19:40:51 GMT
<
* Connection #0 to host localhost left intact
According to RFC2616 sc 14.13 this needs to be non-null.
2:55 p.m.
On Mar 13, 2015, at 2:47 PM, Bernd Eckenfels
<ecki(a)zusammenkunft.net> wrote:
Hello,
with all versions I tried (including 1.2.0.Beta9) undertow-core will
return content-length: 0 if a HEAD request is made.
-snip-
< HTTP/1.1 200 OK
< Connection: keep-alive
< Last-Modified: Fri, 13 Mar 2015 19:24:58 GMT
< Content-Length: 0
< Content-Type: text/xml
< Date: Fri, 13 Mar 2015 19:40:51 GMT
<
* Connection #0 to host localhost left intact
According to RFC2616 sc 14.13 this needs to be non-null.
It’s wasting bandwidth, so we should probably not send it. However, its a legal value:
14.13 says "Any Content-Length greater than or equal to zero is a valid value."
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
3:20 p.m.
Hello Jason,
yes you could send a wrong value and it would be
better to not answer one than a wrong one, but even better woild it
be to follow the RFC recommendation, that states that the headers of a
HEAD should be identical to those of a GET. In fact the content-length
is one of the most interesting informations one would want to query
with a HEAD request.
Gruss
Bernd
Am Fri, 13 Mar 2015 14:55:39 -0500
schrieb Jason Greene <jason.greene(a)redhat.com>:
> On Mar 13, 2015, at 2:47 PM, Bernd Eckenfels
> <ecki(a)zusammenkunft.net> wrote:
>
> Hello,
>
> with all versions I tried (including 1.2.0.Beta9) undertow-core will
> return content-length: 0 if a HEAD request is made.
>
-snip-
> < HTTP/1.1 200 OK
> < Connection: keep-alive
> < Last-Modified: Fri, 13 Mar 2015 19:24:58 GMT
> < Content-Length: 0
> < Content-Type: text/xml
> < Date: Fri, 13 Mar 2015 19:40:51 GMT
> <
> * Connection #0 to host localhost left intact
>
> According to RFC2616 sc 14.13 this needs to be non-null.
>
It’s wasting bandwidth, so we should probably not send it. However,
its a legal value:
14.13 says "Any Content-Length greater than or equal to zero is a
valid value."
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
3:29 p.m.
Ah! now i follow. Sorry, I skimmed your email and didn’t recognize you were highlighting
the discrepancy between a GET and HEAD.
On Mar 13, 2015, at 3:20 PM, Bernd Eckenfels
<ecki(a)zusammenkunft.net> wrote:
Hello Jason,
yes you could send a wrong value and it would be
better to not answer one than a wrong one, but even better woild it
be to follow the RFC recommendation, that states that the headers of a
HEAD should be identical to those of a GET. In fact the content-length
is one of the most interesting informations one would want to query
with a HEAD request.
Gruss
Bernd
Am Fri, 13 Mar 2015 14:55:39 -0500
schrieb Jason Greene <jason.greene(a)redhat.com>:
>
>> On Mar 13, 2015, at 2:47 PM, Bernd Eckenfels
>> <ecki(a)zusammenkunft.net> wrote:
>>
>> Hello,
>>
>> with all versions I tried (including 1.2.0.Beta9) undertow-core will
>> return content-length: 0 if a HEAD request is made.
>>
>
> -snip-
>
>> < HTTP/1.1 200 OK
>> < Connection: keep-alive
>> < Last-Modified: Fri, 13 Mar 2015 19:24:58 GMT
>> < Content-Length: 0
>> < Content-Type: text/xml
>> < Date: Fri, 13 Mar 2015 19:40:51 GMT
>> <
>> * Connection #0 to host localhost left intact
>>
>> According to RFC2616 sc 14.13 this needs to be non-null.
>>
>
> It’s wasting bandwidth, so we should probably not send it. However,
> its a legal value:
>
> 14.13 says "Any Content-Length greater than or equal to zero is a
> valid value."
>
> --
> Jason T. Greene
> WildFly Lead / JBoss EAP Platform Architect
> JBoss, a division of Red Hat
>
_______________________________________________
undertow-dev mailing list
undertow-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/undertow-dev
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
4:10 p.m.
Hello Jason,
oh ok, no problem. I was trying to fix it myself by adding a
content-length header in ResourceHandler#serveResource in the" if
(!sendContent)", but it seems the core is overwriting this.
Want me to open a bug for it?
Gruss
Bernd
Am Fri, 13 Mar 2015 15:29:55 -0500
schrieb Jason Greene <jason.greene(a)redhat.com>:
Ah! now i follow. Sorry, I skimmed your email and didn’t recognize
you were highlighting the discrepancy between a GET and HEAD.
> On Mar 13, 2015, at 3:20 PM, Bernd Eckenfels
> <ecki(a)zusammenkunft.net> wrote:
>
> Hello Jason,
>
> yes you could send a wrong value and it would be
> better to not answer one than a wrong one, but even better woild it
> be to follow the RFC recommendation, that states that the headers
> of a HEAD should be identical to those of a GET. In fact the
> content-length is one of the most interesting informations one
> would want to query with a HEAD request.
>
> Gruss
> Bernd
>
> Am Fri, 13 Mar 2015 14:55:39 -0500
> schrieb Jason Greene <jason.greene(a)redhat.com>:
>
>>
>>> On Mar 13, 2015, at 2:47 PM, Bernd Eckenfels
>>> <ecki(a)zusammenkunft.net> wrote:
>>>
>>> Hello,
>>>
>>> with all versions I tried (including 1.2.0.Beta9) undertow-core
>>> will return content-length: 0 if a HEAD request is made.
>>>
>>
>> -snip-
>>
>>> < HTTP/1.1 200 OK
>>> < Connection: keep-alive
>>> < Last-Modified: Fri, 13 Mar 2015 19:24:58 GMT
>>> < Content-Length: 0
>>> < Content-Type: text/xml
>>> < Date: Fri, 13 Mar 2015 19:40:51 GMT
>>> <
>>> * Connection #0 to host localhost left intact
>>>
>>> According to RFC2616 sc 14.13 this needs to be non-null.
>>>
>>
>> It’s wasting bandwidth, so we should probably not send it. However,
>> its a legal value:
>>
>> 14.13 says "Any Content-Length greater than or equal to zero is a
>> valid value."
>>
>> --
>> Jason T. Greene
>> WildFly Lead / JBoss EAP Platform Architect
>> JBoss, a division of Red Hat
>>
>
>
> _______________________________________________
> undertow-dev mailing list
> undertow-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/undertow-dev
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
5:02 p.m.
Hello,
I filed this bug: https://issues.jboss.org/browse/UNDERTOW-409
Gruss
Bernd
BTW: I just noticed dont be confused about my cut+paste example below,
I was renaming /webdav into /res to avoid the confusing path
name /webdav. However I did not change all occurences. So both
requests actually are run against the same /res resource (and should
show the same size).
4:05 p.m.
I have fixed this upstream.
Stuart
----- Original Message -----
From: "Bernd Eckenfels" <ecki(a)zusammenkunft.net>
To: undertow-dev(a)lists.jboss.org
Sent: Sunday, 15 March, 2015 9:02:47 AM
Subject: Re: [undertow-dev] ResourceHandler give 0 byte Content-Length for HEAD
Hello,
I filed this bug: https://issues.jboss.org/browse/UNDERTOW-409
Gruss
Bernd
BTW: I just noticed dont be confused about my cut+paste example below,
I was renaming /webdav into /res to avoid the confusing path
name /webdav. However I did not change all occurences. So both
requests actually are run against the same /res resource (and should
show the same size).
_______________________________________________
undertow-dev mailing list
undertow-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/undertow-dev
3552
days inactive
3554
days old
6 comments
3 participants
participants (3)
-
Bernd Eckenfels -
Jason Greene -
Stuart Douglas