mitre / mitre/HTTP-Proxy-Servlet
TargetURI needs to be configured outside of the WAR/EAR
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.5k
- Forks
- 557
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I've got a requirement that the WAR/EAR can't be modified from DEV to PRODUCTION.
So I need that the targetURI can be configured outside of the WAR/EAR.
For example, all the properties of the application is read from Linux FS : /apps/configuration/web/myApp.properties
Is it possible out of the box?
Can it be configured after the container startup? Any sample code to do that?
Project is not using SpringMVC.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Begin by locating the servlet's targetURI configuration and startup initialization; the issue provides no file or test names. Verify whether /apps/configuration/web/myApp.properties can supply targetURI outside the WAR/EAR, including after container startup, and document a working sample or mark the behavior unsupported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100