Error page does not include sendError(status, message) message if custom reason phrase is disabled.

[arinban]

GlassFish makes the custom reason phrase disabled if the following jvm option is set to GlassFish.

-Dorg.apache.coyote.USE_CUSTOM_STATUS_MSG_IN_HEADER=false

According to Java Doc of HttpServletResponse, error page generated by sendError API contains the message.

In grizzly implementation, allowCustomReasonPhrase flag in HttpResponsePacket influences both the reason phrase(ex. HTTP/1.1 404 REASON) and the error page generated by the web container.
Therefore, the error page does not include the message if the jvm option is set.

On the other hand, in grizzly 1.9.X and GlassFish 3.1.2.2, allowCustomReasonPhrase works only to the reason phrase.
So the error page include the message even if the jvm option is configured.

Is the behavior of latest grizzly right?

Affected Versions

[2.3.15]

[arinban]

@glassfishrobot Commented
Reported by yama0428

[arinban]

@glassfishrobot Commented
This issue was imported from java.net JIRA GRIZZLY-1825

[arinban]

• Issue Imported From: Error page does not include sendError(status, message) message if custom reason phrase is disabled. javaee/grizzly#1825
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To:@glassfishrobot