Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.php > #3387
| From | Bill B <me@privacy.net> |
|---|---|
| Newsgroups | comp.lang.php |
| Subject | Re: .htaccess vs PHP header(location:) |
| Date | 2011-10-11 07:49 -0400 |
| Organization | A noiseless patient Spider |
| Message-ID | <j71afc$bg9$1@dont-email.me> (permalink) |
| References | <0ja7975a0ieulqube5a6cc6fqrdqiir7nr@4ax.com> <j70bum$d1j$1@dont-email.me> |
On 10/10/2011 11:08 PM, Jerry Stuckle wrote: > On 10/10/2011 10:40 PM, Michael Joel wrote: >> I am wanting to control access to my site. >> Sometimes I want the site "off" with visitors redirected to a folder. >> >> I have been using htaccess but have written a php script to automate >> the site's on/off control. I am considering using php at the top of >> each page instead of htaccess. >> >> basic outline: >> my script creates a file when the site is to close. It contains the >> reason for closing (text), close time (timestamp), and re-open time >> (timestamp). (...I could also have the script create an htaccess file >> if that is decided to be best...) >> >> My thought is to, instead of use htaccess for the redirect, simple >> place a PHP file_exists() check at top of every page on the site >> (scripts as well). If the file exists then header (location: >> xxxxxxxxx) is used to force a redirect. >> >> The advantage to this is: >> 1) I had help making the htaccess file - I haven't a clue what all the >> jibberish means. So changing the access to allow certain areas open or >> not is not easy. I would like to find a simple PDF doc that would give >> simple explanations on it. >> >> 2) it would allow a lot of control on what to close. I simple don't >> include the check on pages/scripts I want to remain "open". >> >> I did wonder if the file_exists check would cause a large slow down on >> serving pages? >> >> Thanks >> Mike > > No, it shouldn't require a lot of overhead to check to see if a file > exists. Such an option should work fine, as long as you remember to > include it every time. > > However - if you're going to be doing web work, you need to learn some > basic things like coding some simple things in .htaccess to be > effective. So I would also recommend you spend a little time learning > that. It's not too hard once you get the hang of it. Can it be as simple as setting $open_for_business to zero or one in a file named "can_enter.php", including the file, and allowing access to pages based on the value of $open_for_business? Bill B
Back to comp.lang.php | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
.htaccess vs PHP header(location:) Michael Joel <no@please.com> - 2011-10-10 22:40 -0400
Re: .htaccess vs PHP header(location:) Jerry Stuckle <jstucklex@attglobal.net> - 2011-10-10 23:08 -0400
Re: .htaccess vs PHP header(location:) Michael Joel <no@please.com> - 2011-10-10 23:33 -0400
Re: .htaccess vs PHP header(location:) Bill B <me@privacy.net> - 2011-10-11 07:49 -0400
Re: .htaccess vs PHP header(location:) The Natural Philosopher <tnp@invalid.invalid> - 2011-10-11 14:56 +0100
Re: .htaccess vs PHP header(location:) The Natural Philosopher <tnp@invalid.invalid> - 2011-10-11 09:15 +0100
Re: .htaccess vs PHP header(location:) Jerry Stuckle <jstucklex@attglobal.net> - 2011-10-11 06:02 -0400
csiph-web