HEAD response not returning same headers as GET response

[colin-adams]

The GET response has Date, Server, Content-length and Content-type. The HEAD response only has the first two.
Server is provided by Apache (this is libfcgi connector).

Debugging shows that at the time of committing the response, the WSF_HEAD_RESPONSE_WRAPPER.header has all three fields.

Perhaps this is a problem with libfcgi or Apache, rather than EWF.

Needs further investigation.

[colin-adams]

I can reproduce the problem with Nino.
In this case, the only headers returned on the HEAD response are Connection: close.

[colin-adams]

And in fact the RestbucksCRUD example exhibits this behaviour.

Compare:

curl -v http://localhost:9090/api/doc >/temp.html

and

curl -v -I http://localhost:9090/api/doc >/temp.html

[jocelyn]

Indeed there is a bug with delayed header sending AND WSF_HEAD_...
implementation.

I'll fix that before the end of this week.

On Tue, Apr 9, 2013 at 5:41 PM, colin-adams notifications@github.comwrote:

And in fact the RestbucksCRUD example exhibits this behaviour.

Compare:

curl -v http://localhost:9090/api/doc >/temp.html

and

curl -v -I http://localhost:9090/api/doc >/temp.html

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/53#issuecomment-16120706
.

[jocelyn]

I think this is now fixed by commit f85dc7f

[colin-adams]

Confirmed.