Mailing List Archive: Cherokee: dev

Issue 263 in cherokee: Reverse Proxy: Location header should be remaped to its own address space.

Index | Next | Previous | View Threaded

codesite-noreply at google

Sep 27, 2009, 5:47 AM

Post #1 of 9 (633 views)
Permalink

Issue 263 in cherokee: Reverse Proxy: Location header should be remaped to its own address space.

Comment #3 on issue 263 by praseodym: Reverse Proxy: Location header should
be remaped to its own address space.
http://code.google.com/p/cherokee/issues/detail?id=263

Doesn't yet work in 0.99.22.

--
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
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Sep 27, 2009, 6:07 AM

Post #2 of 9 (601 views)
Permalink

Issue 263 in cherokee: Reverse Proxy: Location header should be remaped to its own address space. [In reply to]

Comment #4 on issue 263 by ste...@konink.de: Reverse Proxy: Location header
should be remaped to its own address space.
http://code.google.com/p/cherokee/issues/detail?id=263

Since we are at 0.99.24 and there is reply rewriting. What doesn't work?

--
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
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Sep 27, 2009, 7:47 AM

Post #3 of 9 (596 views)
Permalink

Issue 263 in cherokee: Reverse Proxy: Location header should be remaped to its own address space. [In reply to]

Comment #5 on issue 263 by praseodym: Reverse Proxy: Location header should
be remaped to its own address space.
http://code.google.com/p/cherokee/issues/detail?id=263

0.99.22 should have reply rewriting since it was released only a month ago.
My setup is Jetty with a Cherokee
HTTP reverse proxy. A sample request:

$ curl -i http://example.com/test
HTTP/1.1 302 Moved Temporarily
Connection: Keep-Alive
Keep-Alive: timeout=15
Transfer-Encoding: chunked
Date: Sun, 27 Sep 2009 14:44:59 GMT
Location: http://localhost:9920/test/
Server: Jetty(6.1.x)

--
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
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Sep 27, 2009, 7:56 AM

Post #4 of 9 (588 views)
Permalink

Issue 263 in cherokee: Reverse Proxy: Location header should be remaped to its own address space. [In reply to]

Comment #6 on issue 263 by ste...@konink.de: Reverse Proxy: Location header
should be remaped to its own address space.
http://code.google.com/p/cherokee/issues/detail?id=263

So did you configure reply rewriting ;)

--
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
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Sep 27, 2009, 8:43 AM

Post #5 of 9 (604 views)
Permalink

Issue 263 in cherokee: Reverse Proxy: Location header should be remaped to its own address space. [In reply to]

Comment #7 on issue 263 by praseodym: Reverse Proxy: Location header should
be remaped to its own address space.
http://code.google.com/p/cherokee/issues/detail?id=263

Hmm, I didn't know that I had to configure it manually. I don't really like
how it works though, manual find-
replace rules won't work with multiple hostnames. For what it's worth,
nginx handles the same situation without
problems.

--
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
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Sep 27, 2009, 8:47 AM

Post #6 of 9 (604 views)
Permalink

Issue 263 in cherokee: Reverse Proxy: Location header should be remaped to its own address space. [In reply to]

Comment #8 on issue 263 by ste...@konink.de: Reverse Proxy: Location header
should be remaped to its own address space.
http://code.google.com/p/cherokee/issues/detail?id=263

So in your ideal situation what should be replaced then? Since obviously
you could
rewrite the request, the redirect can contain internal and external
hostnames, so per
definition if you want to rewrite the request to something useful you have
to know
what you want to rewrite.

--
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
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Sep 27, 2009, 9:16 AM

Post #7 of 9 (588 views)
Permalink

Issue 263 in cherokee: Reverse Proxy: Location header should be remaped to its own address space. [In reply to]

Comment #9 on issue 263 by praseodym: Reverse Proxy: Location header should
be remaped to its own address space.
http://code.google.com/p/cherokee/issues/detail?id=263

For a request to http://example.com/test I'd expect it to be redirected to
http://example.com/test/, not
http://localhost:9920/test/. Since the proxied server is at localhost:9920,
Cherokee should be able to figure out
that a redirect there makes no sense, and instead rewrite it to the
originally requested domain.

--
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
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Sep 27, 2009, 9:32 AM

Post #8 of 9 (592 views)
Permalink

Issue 263 in cherokee: Reverse Proxy: Location header should be remaped to its own address space. [In reply to]

Comment #10 on issue 263 by ste...@konink.de: Reverse Proxy: Location
header should be remaped to its own address space.
http://code.google.com/p/cherokee/issues/detail?id=263

The location is generated by your 'backend' right? If the backend would
generate a
'valid' location you don't want to have it redirected. So I kind of think
it is
completely 'correct' to set up a reply rewriter manually.

I wonder if it was the intention of r2979 to do this automatically.

--
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
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Sep 27, 2009, 10:48 AM

Post #9 of 9 (607 views)
Permalink

Issue 263 in cherokee: Reverse Proxy: Location header should be remaped to its own address space. [In reply to]

Comment #11 on issue 263 by praseodym: Reverse Proxy: Location header
should be remaped to its own address space.
http://code.google.com/p/cherokee/issues/detail?id=263

This is troublesome if I have one virtual host with multiple domains; how
would I rewrite it to the same domain?

The location is indeed generated by the backend as an internal redirection,
since it doesn't 'know' that it's being
proxied. An automatic method would solve most of the causes of wanting this
reply rewriting anyway.

--
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
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads