|
My ISP blocks incoming port 80, so I need to use another port no which I will translate to 80 in the firewall. The problem is I need to go directly to a subdirectory of the webserver, as in
(and I can't make this the default website on that server, because
is also used, for a different website). And apparently you can't use either of these constructions either:
or
...when I try these I get errors. So, how do I allow users to reach
on port 50080? I have set up a redirect (webhop), let's call it
is no more successful than trying with the full url/subdirectory in the address bar. What am I doing wrong? Is there in fact a way to achieve what I'm trying to do? (If it requires restructuring the websites then so be it - if someone can give me pointers here I'm more than willing to give it a whirl) Thanks... |
|
|
|
And you can use a webhop like this: Edit:
No, this is nothing to do with the port 80 block, you aren't hitting this, not at all. |
|
OK, thanks guys... I was afraid someone was going to say something like this. Cry Havok - when I try your suggestion I get a fairly comprehensive (and yet disturbingly unhelpful!) error message - "An error occurredwhen connecting to {...}. SSL received a record that exceeded the maximum permissible length. (Error code: ssl_error_rx_record_too_long). *The page you are trying to view can not be shown because the authenticity of the received data can not be verified *Please contact the web site owners {yada yada yada}" - Apparently this has something to do with the certificate installed in the web server - this is going to be fun to fix but I'll attack it over the weekend... I was hoping the webhop redirect would bypass this problem but, as it happens, not! Too bad :-( RotBlitz - that gets me nowhere I'm afraid! "504 Gateway timeout" (just as if there was no port redirect, i.e. hitting the port 80 block - more or less as expected, the address bar of Firefox changes to the redirected address, complete with /subdirectory, as the error comes up). Thanks to both of you for helping me to understand the correct structure of the URL in a situation like this. Much obliged, I'll buy you both a beer :cheers: |