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

Initialize RequestPath on demand in AbstractServerHttpRequest #33227

Closed
rstoyanchev opened this issue Jul 17, 2024 · 0 comments
Closed

Initialize RequestPath on demand in AbstractServerHttpRequest #33227

rstoyanchev opened this issue Jul 17, 2024 · 0 comments
Assignees
@rstoyanchev
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement
Milestone
6.2.0-M6

Comments

@rstoyanchev
Copy link
Contributor

The path is parsed eagerly at construction with the expectation that it is required. However, that may not always be the case with functional endpoints, and custom routing functions. The initializaiton can be on-demand like other request properties.
@rstoyanchev rstoyanchev added in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement labels Jul 17, 2024
@rstoyanchev rstoyanchev added this to the 6.2.0-M6 milestone Jul 17, 2024
@rstoyanchev rstoyanchev self-assigned this Jul 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rstoyanchev rstoyanchev

Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement
Projects
None yet
Milestone
6.2.0-M6
Development

No branches or pull requests
1 participant
@rstoyanchev