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.

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

Allow Session filter's order and dispatcher types to be configured via the environment #8301

Closed
wilkinsona opened this issue Feb 15, 2017 · 4 comments
Labels
type: enhancement A general enhancement
Milestone

Comments

@wilkinsona
Copy link
Member

No description provided.

@wilkinsona wilkinsona added this to the 2.0.0.M3 milestone Feb 15, 2017
@wilkinsona
Copy link
Member Author

wilkinsona commented Jul 24, 2017

Having just spent a bit of time looking at Session's reactive support, there's no equivalent of the servlet filter order and servlet filter dispatcher types there. Instead a custom WebSessionManager is plugged into a WebFlux HttpHandler and that's pretty much it. In short, the properties proposed here are Servlet-specific.

We already have similar properties for configuring the security filter:

security.filter-order
security.filter-dispatcher-types

I don't think we want to follow that precedent as it leaves the servlet specific properties as siblings of all the other properties.

I wonder if this is sufficient to distinguish the properties as Servlet-specific:

spring.session.filter.order
spring.session.filter.dispatcher-types

Or do we need to go a step further:

spring.session.servlet.filter-order
spring.session.servlet.filter-dispatcher-types

Or even:

spring.session.servlet.filter.order
spring.session.servlet.filter.dispatcher-types

@snicoll
Copy link
Member

snicoll commented Jul 25, 2017

Whenever I do this, I always have a look at the appendix to find a pattern. We do have server.servlet so spring.session.servlet fits nicely. I'd be in favour of the second proposal, I am not sure the extra namespace is warranted.

@vpavic
Copy link
Contributor

vpavic commented Jul 25, 2017

I'm also in favor of spring.session.servlet. It clearly communicates that the containing properties apply to Spring Session's Servlet API integration.

@wilkinsona
Copy link
Member Author

Thanks, both. spring.session.servlet.filter-order and spring.session.servlet.filter-dispatcher-types it is then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

3 participants