Suggestion: One property to define the properties of different servers
See original GitHub issueSpring boot 2.4.x
As was done in this issue, where the configuration of the management context-path for Tomcat and Netty servers was unified under the property management.server.base-path
, does it make sense to do the same for the other properties?
For example:
With server.servlet.context-path
and spring.webflux.base-path
or server.tomcat.connection-timeout
and server.netty.connection-timeout
among others…
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
How to maintain a single property file for multiple web server ...
I am maintaining/developing a web application which is deployed in multiple nodes of a websphere cell. There are two nodes in a WAS...
Read more >How to set up a resource property | Microsoft Learn
Resource property list is an object that contains multiple resource properties as its member (msDS-MembersOfResourcePropertyList). It is used to ...
Read more >Server properties—ArcGIS REST APIs
ArcGIS Server has configuration properties that govern some of its behavior. The properties resource is a container for these properties.
Read more >Properties overview - Heap Help Center
Properties are bits of metadata that are captured during user interactions with your app. Heap automatically captures a wide variety of ...
Read more >create-system-properties - Oracle Help Center
When a domain supports multiple servers, the override potential can be exploited. When a domain is started or restarted, all <system-property> elements are ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
We’ve discussed the connection timeout properties in the past (see #18473) and decided it was best to keep them separate.
I’m personally not too keen on unifying
server.servlet.context-path
andspring.webflux.base-path
since they are well defined terms already. The Servlet property is especially nice at the moment because it maps well tojavax.servlet.ServletContext.getContextPath()
. If we rename it we break that link and we don’t get a huge benefit unless users are switching between Servlet and WebFlux apps often.Flagging to see what others in the team think.
The consensus seems to be that it’s best to keep the properties as they are (at least for now). Thanks anyway for the suggestion.