-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable URL Rewriting by default with Servlet 3.0 config #179
Comments
Closed
2 tasks
How about <session-config>
<cookie-config>
<!-- <secure>true</secure> -->
<http-only>true</http-only>
</cookie-config>
<tracking-mode>COOKIE</tracking-mode>
</session-config> ? |
It's better so I modified the possible solution. |
👍 |
ikeyat
added a commit
that referenced
this issue
Oct 29, 2015
kazuki43zoo
added a commit
that referenced
this issue
Oct 29, 2015
…riting_servlet3 Add config to disable URL rewriting by default #179
making
added a commit
that referenced
this issue
Oct 30, 2015
…riting_servlet3_backport_5.0.x Add config to disable URL rewriting by default #179
This was referenced Oct 30, 2015
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
In general, URL rewriting should be disabled for security reasons.
Spring security has option to disable it.
On the other hand, Servlet 3.0 introduced a configuration to disable URL rewriting in web.xml with following code. It's better to defense at lower layer if possible, so we should apply this to our blank project as default configurations.
Secure
attribute can be configured with<secure>true</secure>
. But we had better avoid to define it.The reason is that most enterprise applications decode/encode HTTPS on SSL accelerator, LB or HTTP server. In such cases, the
Secure
attribute affects and a browser ignores cookie when it is running without them. Application should be independent from infrastructures.Possible Solutions
Add following config on web.xml.
Affects Version/s
Fix Version/s
Issue Links
Reference Links
The text was updated successfully, but these errors were encountered: