UrlRewrite Google Group

Re: redirect with status code 307 (for POST)

2009-11-06T17:34:24Z

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)

2009-11-06T08:18:07Z

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)

2009-11-06T02:19:42Z

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

Cheers
Avlesh

Re: [?] get params to the url rewrite

2009-11-06T02:17:36Z

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

2009-11-05T08:28:04Z

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)

2009-11-05T14:21:56Z

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)

2009-11-05T14:20:10Z

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

thanks,
Colin

Re: redirect with status code 307 (for POST)

2009-11-05T12:32:47Z

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)

2009-11-05T11:10:49Z

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)

2009-11-05T10:49:29Z

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)

2009-11-05T04:24:21Z

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]

Re: redirect with status code 307 (for POST)

2009-11-04T09:03:46Z

Hi,
I think "redirect" could work, but I'm not sure. Are you sure you're
using a version of the servlet API that supports 307?
Version 3.2 is plenty stable btw, I'd recommend upgrading.
It should. But keep in mind that POST after POST has always been a bit
buggy and is only supposed to work on HTTP/1.1 clients. How about

When is UrlRewriteFilter 3.2 stable version releasing

2009-11-03T23:25:35Z

I was wondering when/if we are going to get a stable version of the
3.2 UrlRewriteFilter released?
We are looking to upgrade and were concerned that its not yet in the
maven central repository.
Thanks

redirect with status code 307 (for POST)

2009-11-03T00:04:59Z

Hello,

I'm working on some REST style webservices and trying to use the
UrlRewrite tool to help map some old urls to the new ones. It seems
like the perfect tool for this.

What I need to do is return a redirect status code when the client
POSTs data to certain URLs. I want the client to re-POST the data to

Re: URL Redirect 301

2009-11-03T10:03:57Z

It can't get simpler than this. I would recommend going through the manual
in future (
[link])
before asking questions on the mailing list.
The rule underneath in your urlrewrite.xml file should do the trick -
<rule>
<from>/product/test-