Web Images Videos Maps News Shopping Gmail more »
Recently Visited Groups | Help | Sign in
Google Groups Home
Issue 39 in urlrewritefilter: Strange behavior of wildcards **
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  2 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
codesite-nore...@google.com  
View profile  
 More options Jun 29, 10:39 am
From: codesite-nore...@google.com
Date: Mon, 29 Jun 2009 14:39:00 +0000
Subject: Issue 39 in urlrewritefilter: Strange behavior of wildcards **
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 39 by e.cerv...@sourcesense.com: Strange behavior of wildcards **
http://code.google.com/p/urlrewritefilter/issues/detail?id=39

I am using the tuckey urlrewriter 3.1.0 and I set up the following rule.

<rule match-type="wildcard">
   <from>/nl/**</from>
   <to type="permanent-redirect">/$1</to>
</rule>

I would simply like to strip away the 'nl' part of my url and leave the
rest, but if slashes are present, with $1 only the first piece is
retrieved. As a result if I consider the http request coming in
nl/blabla1/blabla2?param=3 this will be translated in blabla1

Is this the expected behavior? What shall I do in order to retrieve the
part of the url following the nl/ ?

Thank you very much.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Avlesh Singh  
View profile  
 More options Jun 29, 11:34 am
From: Avlesh Singh <avl...@gmail.com>
Date: Mon, 29 Jun 2009 21:04:32 +0530
Local: Mon, Jun 29 2009 11:34 am
Subject: Re: Issue 39 in urlrewritefilter: Strange behavior of wildcards **

Is this an "issue"?
You should have asked this question first on the mailing list. Filing a bug
comes in much later.

Read up on how the wildcard matching engine works
here<http://tuckey.org/urlrewrite/manual/3.0/#wildcard>
.

A simple solution (with the default "regex" match type) to your problem
could be these two rules underneath:

<!-- this is match all your url's with a queryString -->
<rule>
    <from>^/nl/(.*)\?(.*)$</from>
    <to>/$1?$1&amp;$2</to>
</rule>

<rule>
    <from>^/nl/(.*)$</from>
    <to>/$1</to>
</rule>

A similar solution was posted recently here -
http://www.nabble.com/revised-question-td24209680.html

Cheers
Avlesh


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google