Review ServerProperties and document keys that only work in certain environments
See original GitHub issueCurrently ServerProperties contains quite a mix of things. We’ll need to refactor it to get cleaner reactive/servlet concerns.
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
ITN 200 Midterm Flashcards - Quizlet
Study with Quizlet and memorize flashcards containing terms like Q: Storage pinning is the process of planning hardware for a specific server within...
Read more >Core Features - Spring
This section dives into the details of Spring Boot. Here you can learn about the key features that you may want to use...
Read more >Use Keyboard Shortcuts To Review Documents - myIPRO
Hotkeys, otherwise known as keyboard shortcuts, allow reviewers to quickly apply tags and navigate through documents when working in a batch.
Read more >Install Power BI Report Server - Microsoft Learn
Selecting Power BI Report Server key displays a dialog containing your product key. ... There are only a few steps to install the...
Read more >SSL Cipher Configuration - removing weak ciphers - PaperCut
SSL Protocols and Cipher Suites can be easily configured by editing the server.properties file found in the application directory.
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

Looking at the current properties arrangement, it seems that:
server.display-nameis only applied to Servlet environments, and should move to theserver.servletnamespaceserver.tomcat.redirect-context-root,server.tomcat.use-relative-redirectsandserver.tomcat.additional-tld-skip-patternsare only applied to Servlet environments; I don’t think we really need to move those under aserver.tomcat.servletnamespace…We’ve reviewed this issue and we’ve explored a few options that would guide users towards which environment is supported for a given key. Unfortunately, none of those options are satisfactory. It really feels like #4818 and we believe documenting the keys that are limited to certain environments is a more pragmatic approach to this issue.
This can be a simple extension of the key description with a standard message for now. Perhaps doing this work will give us improvement ideas for the metadata format that we can implement in a future feature release.