Navigation

Stress

Well, here we are in June. I have several projects going, as well as WiredCMS. There also is a much larger "project" at hand - my wedding!

3 weeks from Saturday I will finally be getting married, and I can stop worrying about where money is coming from for all of the vendors. This cannot happen fast enough!

To keep myself sane, Ive been working on WiredCMS in my spare time (which hasn't been too much, paid projects come before personal - of course).

I found an Issue with the SessionManager script I posted a few weeks back, and I couldn't put my finger on the issue. It seemed to be randomly expiring my session any time up to the actual expiration time, and there was not pattern to it. It was probably just an issue with the database. Anyways, I went back to allowing PHP to manager the sessions for the time being, as Database storage only really makes a difference on load balancing web servers.

I also read a blog of a developer who is completely against using the PHP function

  1. header('Location:');

in any situation other than the page has been moved.

He goes on to say this is against standards, as the location string passes the HTML code 302 to the browser. This code indicates that the page is temporarily moved or unavailable.

After reading this, I started thinking about my own uses of the function, and read up on HTML status codes.

I found that using:

  1. header('Location '.$url, true, 303);

Sends an HTML status 303 code - See Other. This seems to be more standard, and will not give the wrong status code for redirecting to another page - eg. from a log in form.

Just thought I would share this with others, in case you are as obsessed with standards as I am.

RjkFkozsmUag