Solved

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

Posted on 2008-06-16
3
213 Views
Last Modified: 2008-06-17
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
Comment
Question by:Ryan Bayne
3 Comments
 

Assisted Solution

by:qaelan
qaelan earned 50 total points
Comment Utility
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
 
LVL 14

Accepted Solution

by:
Tchuki earned 150 total points
Comment Utility
>> 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
 
LVL 2

Author Comment

by:Ryan Bayne
Comment Utility
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

Enabling OSINT in Activity Based Intelligence

Activity based intelligence (ABI) requires access to all available sources of data. Recorded Future allows analysts to observe structured data on the open, deep, and dark web.

Join & Write a Comment

Introduction Many web sites contain image galleries; a common design for these galleries includes a page with a collection of thumbnail images.  You can click on each of the thumbnail images to see the larger version of the image.  This is easily i…
Since pre-biblical times, humans have sought ways to keep secrets, and share the secrets selectively.  This article explores the ways PHP can be used to hide and encrypt information.
Learn how to match and substitute tagged data using PHP regular expressions. Demonstrated on Windows 7, but also applies to other operating systems. Demonstrated technique applies to PHP (all versions) and Firefox, but very similar techniques will w…
The viewer will learn how to create and use a small PHP class to apply a watermark to an image. This video shows the viewer the setup for the PHP watermark as well as important coding language. Continue to Part 2 to learn the core code used in creat…

744 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now