Github user asfgit commented on the issue:
https://github.com/apache/struts/pull/125
Can one of the admins verify this patch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user yasserzamani commented on the issue:
https://github.com/apache/struts/pull/125
@aleksandr-m , not me but my workmate has used it as an ID for each jsp. I
do not know his work details but in general, he then uses this ID to decide
where he should place the result after an
Github user aleksandr-m commented on the issue:
https://github.com/apache/struts/pull/125
Spoted same
`#context['com.opensymphony.xwork2.dispatcher.HttpServletRequest']` expression
[here](https://stackoverflow.com/q/44291034/1700321). @yasserzamani What do you
use it for?
---
If
Github user yasserzamani commented on the issue:
https://github.com/apache/struts/pull/125
Below is my new design which may be helpful as an example for whom is
affected. Those are about access to
`%{#context['com.opensymphony.xwork2.dispatcher.HttpServletRequest'].requestURI}`.
Github user cnenning commented on the issue:
https://github.com/apache/struts/pull/125
Sounds like a very good idea! A short check showed that my apps are not
affected ð
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
