[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 223
  • Last Modified:

Checking login and redirecting to new header from an included part of the page causes header already sent error

Hey

Well the story is my index page calls a header, cell and footer. The cell being the changing element. I'm now adding member only pages and don't know how to protect the page from unauthorised access.

I use this..

<?php
session_start();
if( @$_SESSION['auth'] !="yes")
{header("Location: ../index.php?cellname=pagecells/noauth.php");
exit();
}
?>

and I call it at the start of the cell file that requires protection. Problem is I get errors regarding the header already being sent.

So any ideas on a better way to structure my page. I have offcourse considered sending logged in users to a new php file totally but once again I would want to use cells in that page. If those cell files exist back to square one they will simply be accessed view the original and free to access index.

Only option is whole range of pages created for users only!

thanks for any advice
0
Ryan Bayne
Asked:
Ryan Bayne
2 Solutions
 
qaelanCommented:
If you are getting errors regarding the headers already being sent, make sure that you are calling the header function before any thing is printed to the browser.
0
 
Vel EousResearch & Development ManagerCommented:
>> Problem is I get errors regarding the header already being sent.

You're getting that message because you are trying to modifiy the browser headers after they have already been sent.  You should be putting it before your HTML.

<?PHP

session_start();
if( @$_SESSION['auth'] !="yes")
{header("Location: ../index.php?cellname=pagecells/noauth.php");
exit();
}

?>

<html>
...
</html>

Creating a "user/members only area" is no more complicated than your cell approach and in the long term more desirable (think of expansion).

For security store the session_id() in a database table on the server and a cookie on the client.  When the user is authenticated, the database table is populated with the user name and session_id() and the cookie with the same.  When a new page is accessed, do a check on the database table that the current user and session_id() match with that of the cookie.
0
 
Ryan BayneWordPress DeveloperAuthor Commented:
OK lots of good stuff there. Tchuk that seems to be my solution thanks a lot. Never done it before or stored cookies on server but I will see what I can do and more questions if I get stuck

cheers
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now