Skip to content
This repository has been archived by the owner on Mar 20, 2021. It is now read-only.

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

Closed
glassfishrobot opened this issue Mar 4, 2016 · 3 comments

Comments

@glassfishrobot
Copy link

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]

@glassfishrobot
Copy link
Author

Reported by yama0428

@glassfishrobot
Copy link
Author

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

@glassfishrobot
Copy link
Author

Closing this as this issue is migrated to eclipse-ee4j/grizzly#1825

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant