So, you're saying that creating a cookie and then fetching the variable from it is as easy as "$_GET[variable]"? Seems like you add at least one step with the cookie thing.
What is this compulsion you have with talking out of your ass?
So, you're saying that creating a cookie and then fetching the variable from it is as easy as "$_GET[variable]"? Seems like you add at least one step with the cookie thing.
What is this compulsion you have with talking out of your ass?
"I predict future happiness for Americans if they can prevent the government from wasting the labors of the people under the pretense of taking care of them."
"The tree of liberty must be refreshed from time to time with the blood of patriots and tyrants."
-- Thomas Jefferson: American Founding Father, clairvoyant and seditious traitor.
It's considered bad form to pass such variables in the query string because an URI beyond 255 characters may not be supported by all clients (the actual limit varies depending on platform and browser)Originally Posted by CitizenCain
So, you're saying that creating a cookie and then fetching the variable from it is as easy as "$_GET[variable]"? Seems like you add at least one step with the cookie thing.
What is this compulsion you have with talking out of your ass?
And, my dear, I know what I'm talking about here and you're the one trolling. As I said before, there is a place for client-side variable storage - and that is the session / cookie. You're trying to shoehorn something into a method it's not meant for. I mean, would you store a username/password hash in the query string as well? That just asks for a cross-site scripting attack. Best not even to begin with such things.
Furthermore, you're forgetting that he has to create a query string somehow. That will become more complicated as he adds more variables.
When the stars threw down their spears
And watered heaven with their tears:
Did he smile his work to see?
Did he who made the lamb make thee?
Posting Permissions
Reply With Quote