-
Notifications
You must be signed in to change notification settings - Fork 388
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
Support war names that contain # symbol denoting sub path. #1359
Comments
@TonyWeston Can you provide details as to what fails? This is vague at best so I need full description of what is not supported including stack traces. Also any pull request you can provide that fixes the situation is most appreciated. If my memory serves me, I thought we addressed this a couple years back so I'm not clear what the issue is with current release. |
Ok, steps to reproduce, on Psiprobe 3.2.0 (built at 2018-12-20T22:06:41Z)
|
Feel free to use this war file for test purposes. |
I have the issue with the two hash marks for the version. However, in psi probe, when I first deploy app##1.0.war, the app will be deployed to /app, but in psi probe its name will be app##1.0.war, and the link will be /app##1.0. The link will open the application because of the hash in the link. As a solution, I think it would be good if psi probe would implement the ##version naming convention. And also show this version in the Applications tab. Exactly like in the apache manager. How else can I see an application's version number in psi probe? |
Tomcat supports contexts that have paths with many sub paths.
As you know, app.war will be deployed to context /app
However, it is also possible to deploy a war to a context that may have multiple sub paths.
app#sub1.war is deployed to context /app/sub1
app#sub2.war is deployed to context /app/sub2
app#sub2#abc.war is deployed to context /app/sub2/abc
Also versions of apps can be specified by using two hash's in the name
app##12.war is deployed to /app
See here for more details:
https://tomcat.apache.org/tomcat-8.0-doc/config/context.html#Naming
Currently, psiprobe struggles with war files named this way.
The text was updated successfully, but these errors were encountered: