Solved! Go to Solution.
Views
Replies
Total Likes
For HTTP to HTTPS a reverse proxy really isn't an option - you have no choice but to do s 301 redirect. You need the browser to make the HTTPS connection - with a reverse proxy the browser would still think it was on a unencrypted page - all you'd be doing is establishing ad SSL connection between you reverse proxy and your web server (which are probably the same boxes).
In case of a normal redirect from old URL to a new one I'd tend to agree that a reverse proxy is overkill. You lose some page rack which you gain back sooner or later, and save yourself endless operational headaches that would come with maintaining the reverse proxy mappings.
Views
Replies
Total Likes
For HTTP to HTTPS a reverse proxy really isn't an option - you have no choice but to do s 301 redirect. You need the browser to make the HTTPS connection - with a reverse proxy the browser would still think it was on a unencrypted page - all you'd be doing is establishing ad SSL connection between you reverse proxy and your web server (which are probably the same boxes).
In case of a normal redirect from old URL to a new one I'd tend to agree that a reverse proxy is overkill. You lose some page rack which you gain back sooner or later, and save yourself endless operational headaches that would come with maintaining the reverse proxy mappings.
Views
Replies
Total Likes
In general, you would use a reverse proxy if you had content on a remote server and the easiest way to make user feel as if content is coming from one single server is using reverse proxy. I don't see that's the case here, also reverse proxy eats up more network bandwidth as compared to 301 redirects.
Also In your case eventually you will need search engines to crawl up and index https. Serving a 301 indicates to both browsers and search engine bots that the page has moved permanently. Search engines interpret this to mean that not only has the page changed location, but has also been updated and updated page/content can be found at the new URL. The engines will carry any link weighting from the original page to the new URL.
So I would suggest go with 301 redirects.
- Runal
Views
Replies
Total Likes
301 redirect would be good... refer this aswell http://stackoverflow.com/questions/8541129/reverse-proxy-vs-301-redirect
Views
Replies
Total Likes
Thanks for inputs.I still have few questions
I have system that is configured as below
[browser]-> [Apache reverse proxy] -> [Apache AEM webserver].
QUESTIONS:-
2. Now for doing a 301 redirect at reverse proxy server
2.a Can I use http://wiki.apache.org/httpd/RedirectSSL where they have suggested use Using virtual hosts (using redirect) instead of mod_rewrite as suggested.
2.b But i don't see any snippet about 301 rule in Using virtual hosts (using redirect) .Could some one help me on this??
Views
Replies
Total Likes
Any inputs on the query I had below??
Views
Replies
Total Likes
Views
Likes
Replies