Jump to content

Encrypt the Query string


andrew_ww

Recommended Posts


Just so people cannot alter the string to bypass the system.  Say I have this:

[code]http://localhost/test%20site/child.php?recordID=1[/code]

There is nothing stopping people from typing:

[code]http://localhost/test%20site/child.php?recordID=23[/code]

and seeing something they are not suppose to see.
Okay, that isn't really anything to do with encryption.

You could use session variables instead of url & GET, and also VALIDATE it.

If they're not allowed to have access to 23, when they try to do that, print an error. You have to check for that stuff.
I'm not sure I understand.

Session variable relate to when a user is logged in - correct ?

I essentially have a master - detail page setup, surely a session variable can only determine if a user can either access page 'child.php' or not.

I cannot see how it could stop 'user1' from typing in a different URL once he's already been logged in and granted a session ?

Okay - thank you.

In this case the site will be used only be a handful of people, so if you can login successfully anything on the site is fair game.  The site will restrict people who are not on a list of pre-approved IP addresses

I guess my paranoia gland was over working.  If it was a simple thing to do I would have implemented it.

Cheers,

Andy.

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.