174 reputation
18
bio website
location
age
visits member for 3 years, 5 months
seen Oct 20 at 21:09

Dec
13
awarded  Popular Question
Jul
8
comment How to make htaccess not redirect to http on form submission
Right. I don't want the "www". I also don't want "index.php". I'll need to play with your suggestion to see if I can make it work right.
Jul
8
comment How to make htaccess not redirect to http on form submission
@ChristopherKarel - which parts of my htaccess can I safely remove and replace with that?
Jul
8
comment How to make htaccess not redirect to http on form submission
Alternatively, do you have a "best practice" solution for forcing HTTPS on everything? I've seen so many approaches to this on the net. Not sure what are the pros and cons of each approach. Suggestions?
Jul
8
comment How to make htaccess not redirect to http on form submission
In the interim, how would I modify this .htaccess so that it doesn't redirect to http on POST? I just realized that POST variables are not retained on redirect, which is probably the reason for my problems.
Jul
8
comment How to make htaccess not redirect to http on form submission
Actually - I'm going to be using a CDN. Maybe public proxy server caching won't matter as much if my resources (style sheets, JS, images) are being served via CDN?
Jul
8
comment How to make htaccess not redirect to http on form submission
@ChristopherKarel - "So a happy medium is to force encryption where you need it, and do nothing where you don't." <-- isn't that what I am doing already?
Jul
8
comment How to make htaccess not redirect to http on form submission
@HBruijn - my concern about caching does not have to do with browser caching. I expect that to work with HTTPS. However, HTTPS won't work with public proxy caching, though -- right? I'm not concerned about the minuscule computational cost of HTTPS; I'm concerned about public proxy caching. And I agree with you about httpd.conf.
Jul
8
asked How to make htaccess not redirect to http on form submission
Aug
23
awarded  Popular Question
Mar
24
awarded  Popular Question
Nov
28
awarded  Notable Question
Jul
28
awarded  Popular Question
Sep
26
accepted SSL - should I just make my entire site secured?
Sep
12
comment SSL - should I just make my entire site secured?
@cjc - if I were to just have some parts of the site as secured (instead of trying to secure the entire site and have issues with mixed content warnings), any tips on best practices? Maybe I put all my resources (css, js, images, etc.) in secured folder? Then secured and unsecured pages can reference those resources. For the secured pages, I won't (hopefully) run into mixed content warnings?
Sep
12
comment SSL - should I just make my entire site secured?
@MadHatter - was having problems with SF. Problem resolved. Thanks.
Sep
12
awarded  Scholar
Sep
12
accepted Fine Tune HTTPD.CONF - server crashing after 100 concurrent connections?
Sep
12
accepted How to stress test web server?
Sep
12
accepted .htaccess: how to remove Cache-Control's “max-age”?