UrlRewrite Google Group

Re: Only working on tomcat instance, not apache

avl...@gmail.com (Avlesh Singh) — Mon, 09 Nov 2009 17:17:41 UT

Are you sure only the UrlRewriteFilter is not working?
Is context path correctly set in your tomcat's server config?
Do you have rules, in your urlrewrite.xml, based on host name?

Cheers
Avlesh

Re: get params to the url rewrite

avl...@gmail.com (Avlesh Singh) — Mon, 09 Nov 2009 17:09:21 UT

Changing your rule to the underneath should work as expected -
<rule>
<from>^/test/(.*)\?(.*)$</from >
<to>/test.do?id=$1&$2</to>
</rule>

To make this work, don't forget to add "use-query-string=true" in the root
node of your urlrewrite.xml file.

Cheers
Avlesh

Only working on tomcat instance, not apache

spooforbra...@gmail.com (Wolf) — Mon, 09 Nov 2009 15:25:16 UT

I apologise if the solution to this is spectacularly simple.

Setup: Apache2 > Mod_JK > Tomcat

I'm trying to use UrlRewriteFilter to prettify URLs. The rules are
working fine when accessing the webapp via localhost:8080/webapp/path
(ie. the tomcat instance) but not when accessing the same webapp via

Re: get params to the url rewrite

babybaby...@gmail.com (baby) — Mon, 09 Nov 2009 10:32:32 UT

Hi,

I am new to URL re-writing. I have the same question. How can i pass
the query parameters to the actual URL

e.g. Here is my rule

now when user provide the URL like : [link]

Re: redirect with status code 307 (for POST)

avl...@gmail.com (Avlesh Singh) — Fri, 06 Nov 2009 17:34:24 UT

You are right, Wim. The behavior turned out to be contrary to my belief and
understanding of the 307 status code. I tested it myself to verify. The only
problem is that command line agents (wget, curl etc) still don't "re-submit"
the post data to new url. This led to the misconception, I initially had.

Re: redirect with status code 307 (for POST)

krom...@gmail.com (Wim De Smet) — Fri, 06 Nov 2009 08:18:07 UT

How about:
[link]

I tried it with a 307. In firebug I'm seeing 2 POSTs and the required
browser behaviour (confirmation before second POST).

regards,
Wim

Re: redirect with status code 307 (for POST)

avl...@gmail.com (Avlesh Singh) — Fri, 06 Nov 2009 02:19:42 UT

I'll try and put up a sample on the web today.

Cheers
Avlesh

Re: [?] get params to the url rewrite

avl...@gmail.com (Avlesh Singh) — Fri, 06 Nov 2009 02:17:36 UT

Are you sure that you want it written that way? Use cases are generally the
reverse!

Anways,

if your answer is yes -
<from>/oc/TaskStart.do\?method =selectTaskMethod&mid=(.*) </from>
<to type="permanent-redirect" last="true">/methods/oc/$1</to >
Don't forget to turn on the "use-query-string" parameter in the root node.

[?] get params to the url rewrite

alexey.petu...@gmail.com (Roublard) — Thu, 05 Nov 2009 08:28:04 UT

Guys, hi!

Have a problem here, kinda novice in url rewriting. Need a rewriting
rule from
/oc/TaskStart.do?method=select TaskMethod&mid=910239095203464 76
to
/methods/oc/91023909520346476

I've tried a lot of reqexps but still have no luck to create it. Could
you please provide me an example?

Re: redirect with status code 307 (for POST)

krom...@gmail.com (Wim De Smet) — Thu, 05 Nov 2009 14:21:56 UT

The <to type="proxy">. I have not used it myself before, but it looks
like it does what you want it to do.
regards,
Wim

Re: redirect with status code 307 (for POST)

colin...@gmail.com (Colin) — Thu, 05 Nov 2009 14:20:10 UT

Can you explain what you mean by "proxying the request"?

thanks,
Colin

Re: redirect with status code 307 (for POST)

krom...@gmail.com (Wim De Smet) — Thu, 05 Nov 2009 12:32:47 UT

I reiterate, I do not think I am misreading it. The RFC specifically
allows for a 307 to result in a POST request, namely here:
"If the 307 status code is received in response to a request other
than GET or HEAD, the user agent MUST NOT automatically redirect the
request unless it can be confirmed by the user, since this might

Re: redirect with status code 307 (for POST)

avl...@gmail.com (Avlesh Singh) — Thu, 05 Nov 2009 11:10:49 UT

You misread it Wim. I'll try to be visual and explain it -

Request-1 (GET/POST/HEAD) -> Location: URL-2; Code: 307 -> Request-2 (ONLY
GET/HEAD)
If Request-1 is POST, then a redirect would also ask for a user confirmation
(this is how 307 differs from 302/303, wherein the requested resource is

Re: redirect with status code 307 (for POST)

krom...@gmail.com (Wim De Smet) — Thu, 05 Nov 2009 10:49:29 UT

Hi,
Actually I think you're missing an important modifier here: "without
interaction with the user". What the standard says is that redirect
works for any type, but in the case of a 307 POST the user client is
not allowed to redirect without asking for user confirmation. POST
after POST does indeed work AFAIK. It just doesn't work very well or

Re: redirect with status code 307 (for POST)

avl...@gmail.com (Avlesh Singh) — Thu, 05 Nov 2009 04:24:21 UT

There is a SLIGHT misunderstanding here. Status code 307 is NOT expected to
work as described in the thread. Underneath is a short snippet from W3 RFC
on status codes. This is what it says on the 3XX series -

This class of status code (3XX) indicates that further action needs to be
For more read here - [link]