java - WildFly 8.2 and 304 Not Modified -


rfc 2616 - "all 1xx (informational), 204 (no content), , 304 (not modified) responses must not include message-body."

after upgrading wildfly 8.2 jboss 5.1, load balancer (written netty 4.0) broke.

cause - wildfly sends response message-body on 304 error:

<html><head><title>error</title></head><body>not modified</body></html> 

netty in accordance rfc 2616 reads header 304, ignore not 0 content-length , left body in socket, error on second read same channel.

i can fix changing response.senderror(304) response.setstatus(304), want know, possible configure wildfly not send message-body on 304 not modified error?

technically, 2xx , 3xx not errors. response codes in ranges 4xx , 5xx errors (client errors , server errors, respectively). so, i'd argue setstatus indeed correct one.

as telling server sending error, not including body, server including 1 itself. because errors (4xx , 5xx) have requirement:

except when responding head request, server should send representation containing explanation of error situation, , whether temporary or permanent condition.


Comments

Popular posts from this blog

toolbar - How to add link to user registration inside toobar in admin joomla 3 custom component -

linux - disk space limitation when creating war file -

How to provide Authorization & Authentication using Asp.net, C#? -