Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Improve documentation about enforcing HTTPS #6820

Open
imod opened this issue Sep 5, 2016 · 3 comments
Open

Improve documentation about enforcing HTTPS #6820

imod opened this issue Sep 5, 2016 · 3 comments
Labels
type: documentation A documentation update
Milestone
3.x

Comments

@imod
Copy link

imod commented Sep 5, 2016 •
edited
Loading

Please enhance the documentation on how to properly enforce HTTPS on cloudfoundry...

[1] only describes some aspects when using tomcat behind a proxy and does not talk about enforcing HTTPS, and what about undertow and jetty?

It seems the only way to really enforce is to use a WebSecurityConfigurerAdapter and call http.requiresChannel().anyRequest().requiresSecure() - but this means I have to explicitly disable for local development.

edit:
[1] http://docs.spring.io/spring-boot/docs/current/reference/html/howto-embedded-servlet-containers.html#howto-customize-tomcat-behind-a-proxy-server
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Sep 5, 2016
@philwebb philwebb added type: documentation A documentation update status: ideal-for-contribution An issue that a contributor can help us with and removed status: waiting-for-triage An issue we've not yet triaged labels Sep 6, 2016
@wilkinsona
Copy link
Member

@lmod What was [1] intended to link to?

@imod
Copy link
Author

imod commented Sep 13, 2016 •
edited
Loading

@wilkinsona sorry! I added the link now

@wilkinsona
Copy link
Member

See also #15046.

@wilkinsona wilkinsona changed the title Improve documentation about enforcing HTTPS on cloudfoundry Improve documentation about enforcing HTTPS Jan 15, 2019
@wilkinsona wilkinsona removed the status: ideal-for-contribution An issue that a contributor can help us with label Jan 15, 2019
@wilkinsona wilkinsona added this to the 2.x milestone Jan 15, 2019
@philwebb philwebb modified the milestones: 2.x, 3.x Aug 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: documentation A documentation update
Projects
None yet
Milestone
3.x
Development

No branches or pull requests
4 participants
@philwebb @imod @wilkinsona @spring-projects-issues