struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Heikki Hyyrö <heikki.hy...@tuni.fi>
Subject Action path prefix rules?
Date Fri, 14 Aug 2020 08:47:27 GMT
Hi,

I am a bit confused about the rules concerning mapping URL paths to 
actions. Let's say that I have a Struts application running at 
example.com with the app name "myApp". Then the usual path to access a 
Struts action named "foo" would presumably be

example.com/myApp/foo.action

Now, it seems to be also possible to access the foo-action even by 
adding a more or less arbitrary path prefix before the app name. E.g. 
also both

example.com/abcde/myApp/foo.action
example.com/some/bogus/prefix/myApp/foo.action

seem to access foo. I am wondering where the rules that allow this are 
defined? What would be the relevant documentation to look into?

As a specifid question, I wonder about links. If the foo-page contains 
e.g. a link created with the url-tag, such as

<s:url action="bar" var="barUrl">
   <s:param name="par" value="#something" />
</s:url>
<s:a href="%{viewCourseUrl}">
   Link to bar-action
</s:a>

the link does not include any "extra" path prefix and always points to 
example.com/myApp/bar.action. I am wondering why this happens? And what 
if I actually would want the link to reflect the actual access URL, 
including any "extra" path prefix (e.g. the link might point to 
example.com/some/bogus/prefix/myApp/bar.action)? Is this possible?


-Heikki


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org


Mime
View raw message