|
Home > Archive > Apache Server configuration support > January 2007 > Strange ProxyPass problem
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Strange ProxyPass problem
|
|
| Ignoramus16482 2007-01-11, 1:32 pm |
| I find a need to access a certain website from work, however, I can
only access it from my home IP. (because it is a torrent tracker that
tracks my IP). So, I made the following directives for my home
httpd.conf to access from my secure https website to that torrent
site:
ProxyPass /Example/ http://www.example.ws/
ProxyPassReverse /Example/ http://www.example.ws/
ProxyPass /TK/ http://www.example.ws/TK/
ProxyPassReverse /TK/ http://www.example.ws/TK/
ProxyPass /pic/ http://www.example.ws/pic/
ProxyPassReverse /pic/ http://www.example.ws/pic/
So when I go to https://mysecurehomesite.com/Example/ I am in fact
accessing www.example.ws.
(as an aside, I was surprised to see the need to define /TK/ and /pic/
redirects, but things did not work without them. I thought the the
first ProxyPassReverse directory should translate it).
Anyway. My question is this. example.ws is a Russian website encoded
in windows 1251 encoding. It works fine in my firefox at home when I
access it directly. However, when I access it from work, it displays
question marks instead of all Russian characters. I have to manually
instruct my browser to force Cyrillic Windows-1251 encoding for EVERY
page that I access. Then I can read those pages.
Why would ProxyPass force loss of page encoding information? Can I do
anything about it?
| |
| shimmyshack 2007-01-11, 1:32 pm |
|
Ignoramus16482 a =E9crit :
> I find a need to access a certain website from work, however, I can
> only access it from my home IP. (because it is a torrent tracker that
> tracks my IP). So, I made the following directives for my home
> httpd.conf to access from my secure https website to that torrent
> site:
>
> ProxyPass /Example/ http://www.example.ws/
> ProxyPassReverse /Example/ http://www.example.ws/
> ProxyPass /TK/ http://www.example.ws/TK/
> ProxyPassReverse /TK/ http://www.example.ws/TK/
> ProxyPass /pic/ http://www.example.ws/pic/
> ProxyPassReverse /pic/ http://www.example.ws/pic/
>
> So when I go to https://mysecurehomesite.com/Example/ I am in fact
> accessing www.example.ws.
>
> (as an aside, I was surprised to see the need to define /TK/ and /pic/
> redirects, but things did not work without them. I thought the the
> first ProxyPassReverse directory should translate it).
>
> Anyway. My question is this. example.ws is a Russian website encoded
> in windows 1251 encoding. It works fine in my firefox at home when I
> access it directly. However, when I access it from work, it displays
> question marks instead of all Russian characters. I have to manually
> instruct my browser to force Cyrillic Windows-1251 encoding for EVERY
> page that I access. Then I can read those pages.
>
> Why would ProxyPass force loss of page encoding information? Can I do
> anything about it?
you could just run a tcp proxy at home, and set up your browser to use
your homes public IP as the proxy. Set a username and password of
course so not just anyone can have access, but that way you will test
your home apache proxy against a tcp socket proxy.
| |
| Ignoramus16482 2007-01-11, 7:33 pm |
| On 11 Jan 2007 09:53:34 -0800, shimmyshack <matt.farey@gmail.com> wrote:
>
> Ignoramus16482 a écrit :
>
> you could just run a tcp proxy at home, and set up your browser to use
> your homes public IP as the proxy. Set a username and password of
> course so not just anyone can have access, but that way you will test
> your home apache proxy against a tcp socket proxy.
>
I do not see the point in this, as I do not want to use my home proxy
for all web access. All I want is to pinpoint the proxypass language
problem.
i
|
|
|
|
|