Summary: | SSI regular expressions not working | ||
---|---|---|---|
Product: | Tomcat 6 | Reporter: | Albert Tumanov <altumano> |
Component: | Catalina | Assignee: | Tomcat Developers Mailing List <dev> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | ||
Priority: | P2 | ||
Version: | 6.0.26 | ||
Target Milestone: | default | ||
Hardware: | PC | ||
OS: | Mac OS X 10.4 |
Description
Albert Tumanov
2010-03-22 11:48:29 UTC
Patches for enhancement requests are always welcome Fixed in 7.0.x and will be included in 7.0.17 onwards. I don't see this being back-ported to 6.0.x or 5.5.x. Hi, I found a bug working with Tomcat, SSI and regular expression that is still unresolved and my work is essential for proper operation: For example: <!--#set var="aux" value="aa12" --> <!--#if expr="$aux=/^aa([a-zA-Z0-9\-_]*)/" --> <!--#set var="aux2" value="$1" --> <!--#endif --> Resulting value:<!--#echo var="aux2" --> In a html file works correctly, but when working on Tomcat, a complex regular expression fails, and the page returns nothing from it. Regards and await your response. (In reply to comment #3) > Hi, I found a bug working with Tomcat, SSI and regular expression that is > still unresolved and my work is essential for proper operation: I do not understand your description. What do you mean by "fails" and what do you mean by "returns nothing"? Please provide: 1. What are the steps to reproduce your problem 2. What is the actual behaviour that you are observing. 3. What do you expect the correct behaviour to be. ======================================= By the way: 1. The actual implementation Regexp matching is in org/apache/catalina/ssi/ExpressionParseTree.java, in method compareBranches() 2. The feature was implemented by r1136231 and r1136399 3. r1136399 was result of discussion in "Re: r1136231" thread on dev@. In archives: http://markmail.org/message/g6ba77x7abkhibnn http://marc.info/?t=130817798400003&r=1&w=2 4. If you can provide a patch for ExpressionParseTree#compareBranches(), it would be faster. (In reply to comment #3) I think I understood what you are asking for. It is a separate issue, so I filed it separately -> bug 53387 I am re-closing this issue as FIXED. |