I have been fighting with this for quite some time now. How can I hide the port in the browsers address bar? I do not want people seeing I would like for it to show as I have been unable to figure this out with mod_rewrite. Any help would be greatly appreciated.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
URL Masking...
- Thread starter Johnb175
- Start date
sleipnir214
Programmer
Are you sure this is possible? The only way for a browser to go to a non-standard HTTP port is by explicitly stating the port in the URL.
Want the best answers? Ask the best questions!
TANSTAAFL!!
Want the best answers? Ask the best questions!
TANSTAAFL!!
- Thread starter
- #3
sleipnir214
Programmer
Are you redirecting the connection? That's largely the equivalent of typing to the URL, which must include the port number as it's non-standard for HTTPS.
Want the best answers? Ask the best questions!
TANSTAAFL!!
Want the best answers? Ask the best questions!
TANSTAAFL!!
- Thread starter
- #5
yes for instance if someone type in it will redirect to I set this up in my apache httpd.conf. redirect /bleh/ I just wanna strip that off the url in the address bar. It is my understanding that this can be done. Any ideas?
- Thread starter
- #7
Actually your kind of stuck, you simply can not mask https over http. Its kind of a wacky thing to do.
Why not run https over its natural port of port 443?
ProxyPass tells apache to fetch the page FOR you which in this case would make the apache connect to the server secure but the user connection to apache insecure(since ssl would terminate at the reverse proxy).
Your not going to be able to do what you are trying to do, your mixing protocols.
Why not run https over its natural port of port 443?
ProxyPass tells apache to fetch the page FOR you which in this case would make the apache connect to the server secure but the user connection to apache insecure(since ssl would terminate at the reverse proxy).
Your not going to be able to do what you are trying to do, your mixing protocols.
- Thread starter
- #11
- Thread starter
- #13
Ok well i created a new index.htm on the default (port 80) website. In that I put the following:
<frameset rows="*" border="0" framespacing="0" frameborder="NO">
<frame src="</frameset>
It of course does hide the real address in the address bar, however it prompts for me to accept the certificate on every image loaded on that webpage. So I have to accept the cert like 14 times. Any ideas?
<frameset rows="*" border="0" framespacing="0" frameborder="NO">
<frame src="</frameset>
It of course does hide the real address in the address bar, however it prompts for me to accept the certificate on every image loaded on that webpage. So I have to accept the cert like 14 times. Any ideas?
That is what I was referring to when I said
The only solution is to lower the security settings in IE.
Code:
...although you make get some wacky 'security error' things if you go in the wrong direction. Test this solution in multiple browsers..The only solution is to lower the security settings in IE.
Correct, you can only bind one name to an ssl ip.
This is due to the fact that SSL is negotiated before the domain name is transferred. It thus binds to the first name it finds with apache.
There are ways around this but they always involve hardware like an SSL accelerator, an F5 proxy box, Alteon stuff etc etc.
This is due to the fact that SSL is negotiated before the domain name is transferred. It thus binds to the first name it finds with apache.
There are ways around this but they always involve hardware like an SSL accelerator, an F5 proxy box, Alteon stuff etc etc.
If I wanted to host multiple sites on the same server, all using port 443 for SSL/TLS, then would it be easy to set up if you had a different IP for each site?
Would it be as simple as changing the IPs listed on the DNS server that contained the authorative details for that site, so that the SSL connections were all coming in on port 443, but on different IPs, or would I need multiple installations of Apache running simultaneously to negotiate all the secure connections?
Thanks.
Would it be as simple as changing the IPs listed on the DNS server that contained the authorative details for that site, so that the SSL connections were all coming in on port 443, but on different IPs, or would I need multiple installations of Apache running simultaneously to negotiate all the secure connections?
Thanks.
Correct, apache can handle multiple SSL connections but each connection requires its own IP if you want it to display properly.
Let me qualify this, if you don't care about security errors you can switch any vhost on a server into SSL but it will take the SSL cert of the FIRST vhost on THAT IP address.
This leads to a mismatch in hostname/certificate hostname. Giving each ssl hostname its own IP removes the problem.
Let me qualify this, if you don't care about security errors you can switch any vhost on a server into SSL but it will take the SSL cert of the FIRST vhost on THAT IP address.
This leads to a mismatch in hostname/certificate hostname. Giving each ssl hostname its own IP removes the problem.
- Status