Solved Http --> https on Apache 2.4

Tieks

Well-Known Member

Reaction score: 134
Messages: 311

A link does not contain private data (in any normal situation).
Security is not my concern, the stuff I have is open to everyone. But what I see sometimes is this: A GET-request comes in on 80, gets redirected to 443. Some following GET's use 443 too, as expected. Then one more GET on port 80 comes in again, gets redirected again, etc. I'm wondering how they do that. They must have some links or bookmarks containing 'http' that the browser doesn't change. It's not in my html or code.

Exactly. I'll keep it open until I see no more requests coming in.
 
OP
astyle

astyle

Daemon

Reaction score: 764
Messages: 1,644

Redirections done on the server do cost extra processor cycles. If the server is a popular one (has popular content), investing a Threadripper or an Epyc would make sense - as well as having the clients connect correctly, or else be turned away.
 

SirDice

Administrator
Staff member
Administrator
Moderator

Reaction score: 13,121
Messages: 39,712

If the server is a popular one (has popular content), investing a Threadripper or an Epyc would make sense
It makes more sense to spread the load over multiple webservers. Never bet all your money on one horse. Multiple servers also make updating easier without taking your site offline.
 
OP
astyle

astyle

Daemon

Reaction score: 764
Messages: 1,644

FWIW, I managed to pull it off without mod_rewrite... I did it with help from Handbook, Section 30.8.3.1. SSL support . Ended up with a self-signed / self-generated SSL cert, Firefox on my Windows laptop complains (Edge doesn't), but for my use case, it's enough. Learning about mod_rewrite was not a waste of time, though - I'm saving that for other use cases. 😤
 
Top