Cookies and alternatives to cookies

[Jimmy Lo]

I'm trying to pass information from one page to the next. I know I can use
cookies. But I also know there are alternatives. I think one of them is
just to pass parameters through the URL. for instance "http://www.bla.com/test.html?parameter1?parameter2"
etc. etc. Where can I find more information about passing parameters through
the URL? Is it called parameters or is there another term for it.

Also, what are the advantages of using the URL to pass info over using cookies
and when should I use which? Thanks very much,

~jimmy.

[Sergey]

The advantage of using URL parameters is that you don't depend on browser
support (or lack of) cookies.
The disadvantage is that it's cumbersome to append parameters to every URL
on every page. And parameters are visible in the browser address box and
therefore easily hackable (not to say that cookies are more secure)
If you use ASP go to www.15seconds.com for tutorials, also search
www.aspfree.com/devlinks/

--
Sergey Kats
http://codebump.net

"Jimmy Lo" <unreal@angband.org> wrote in message
news:3ab635ea$1@news.devx.com...
>
> I'm trying to pass information from one page to the next. I know I can
use
> cookies. But I also know there are alternatives. I think one of them is
> just to pass parameters through the URL. for instance
"http://www.bla.com/test.html?parameter1?parameter2"
> etc. etc. Where can I find more information about passing parameters
through
> the URL? Is it called parameters or is there another term for it.
>
> Also, what are the advantages of using the URL to pass info over using
cookies
> and when should I use which? Thanks very much,
>
> ~jimmy.

[Chris]

The other alternative is to use (hidden) form elements which are accessed
via the Response.Form collection. This is only avail in ASP tho - (however,
so are parms in the querystring, accessed via Response.Querystring).

Hidden form elements are slightly more secure than querystring parms as they
are not visible in the URL, and can be set using javascript at run-time so
(should) not be viewable with 'View source'.

"Sergey" <sctrl@hotmail.com.spam> wrote:
>The advantage of using URL parameters is that you don't depend on browser
>support (or lack of) cookies.
>The disadvantage is that it's cumbersome to append parameters to every URL
>on every page. And parameters are visible in the browser address box and
>therefore easily hackable (not to say that cookies are more secure)
>If you use ASP go to www.15seconds.com for tutorials, also search
>www.aspfree.com/devlinks/
>
>--
>Sergey Kats
>http://codebump.net
>
>"Jimmy Lo" <unreal@angband.org> wrote in message
>news:3ab635ea$1@news.devx.com...
>>
>> I'm trying to pass information from one page to the next. I know I can
>use
>> cookies. But I also know there are alternatives. I think one of them
is
>> just to pass parameters through the URL. for instance
>"http://www.bla.com/test.html?parameter1?parameter2"
>> etc. etc. Where can I find more information about passing parameters
>through
>> the URL? Is it called parameters or is there another term for it.
>>
>> Also, what are the advantages of using the URL to pass info over using
>cookies
>> and when should I use which? Thanks very much,
>>
>> ~jimmy.
>
>

[Robert]

Advantage for Cookie over QueryString is the limitation of length of a string
that can be past with the URL, I believe it is something odd like 129 characters
long. If you need to pass a long string and you are not using a form, then
try to store the string in a cookie so that the next page can fetch the cookie
and the string.

Good Luck!

Robert


"Chris" <chris.mulvey@scotent.co.uk> wrote:
>
>The other alternative is to use (hidden) form elements which are accessed
>via the Response.Form collection. This is only avail in ASP tho - (however,
>so are parms in the querystring, accessed via Response.Querystring).
>
>Hidden form elements are slightly more secure than querystring parms as
they
>are not visible in the URL, and can be set using javascript at run-time
so
>(should) not be viewable with 'View source'.
>
>"Sergey" <sctrl@hotmail.com.spam> wrote:
>>The advantage of using URL parameters is that you don't depend on browser
>>support (or lack of) cookies.
>>The disadvantage is that it's cumbersome to append parameters to every
URL
>>on every page. And parameters are visible in the browser address box and
>>therefore easily hackable (not to say that cookies are more secure)
>>If you use ASP go to www.15seconds.com for tutorials, also search
>>www.aspfree.com/devlinks/
>>
>>--
>>Sergey Kats
>>http://codebump.net
>>
>>"Jimmy Lo" <unreal@angband.org> wrote in message
>>news:3ab635ea$1@news.devx.com...
>>>
>>> I'm trying to pass information from one page to the next. I know I
can
>>use
>>> cookies. But I also know there are alternatives. I think one of them
>is
>>> just to pass parameters through the URL. for instance
>>"http://www.bla.com/test.html?parameter1?parameter2"
>>> etc. etc. Where can I find more information about passing parameters
>>through
>>> the URL? Is it called parameters or is there another term for it.
>>>
>>> Also, what are the advantages of using the URL to pass info over using
>>cookies
>>> and when should I use which? Thanks very much,
>>>
>>> ~jimmy.
>>
>>
>

[Sergey Kats]

I think specs say 2024 bytes.
The limit of 200 characters might be more realistic because some proxies or
browsers might not support long URLs. Although IE was doing fine with 1k
strings.

--
Sergey Kats
http://codebump.net

"Robert" <robertmcdaniel@freeagent.com> wrote in message
news:3ac00999$1@news.devx.com...
>
> Advantage for Cookie over QueryString is the limitation of length of a
string
> that can be past with the URL, I believe it is something odd like 129
characters
> long. If you need to pass a long string and you are not using a form,
then
> try to store the string in a cookie so that the next page can fetch the
cookie
> and the string.
>
> Good Luck!
>
> Robert
>
>
> "Chris" <chris.mulvey@scotent.co.uk> wrote:
> >
> >The other alternative is to use (hidden) form elements which are accessed
> >via the Response.Form collection. This is only avail in ASP tho -
(however,
> >so are parms in the querystring, accessed via Response.Querystring).
> >
> >Hidden form elements are slightly more secure than querystring parms as
> they
> >are not visible in the URL, and can be set using javascript at run-time
> so
> >(should) not be viewable with 'View source'.
> >
> >"Sergey" <sctrl@hotmail.com.spam> wrote:
> >>The advantage of using URL parameters is that you don't depend on
browser
> >>support (or lack of) cookies.
> >>The disadvantage is that it's cumbersome to append parameters to every
> URL
> >>on every page. And parameters are visible in the browser address box and
> >>therefore easily hackable (not to say that cookies are more secure)
> >>If you use ASP go to www.15seconds.com for tutorials, also search
> >>www.aspfree.com/devlinks/
> >>
> >>--
> >>Sergey Kats
> >>http://codebump.net
> >>
> >>"Jimmy Lo" <unreal@angband.org> wrote in message
> >>news:3ab635ea$1@news.devx.com...
> >>>
> >>> I'm trying to pass information from one page to the next. I know I
> can
> >>use
> >>> cookies. But I also know there are alternatives. I think one of them
> >is
> >>> just to pass parameters through the URL. for instance
> >>"http://www.bla.com/test.html?parameter1?parameter2"
> >>> etc. etc. Where can I find more information about passing parameters
> >>through
> >>> the URL? Is it called parameters or is there another term for it.
> >>>
> >>> Also, what are the advantages of using the URL to pass info over using
> >>cookies
> >>> and when should I use which? Thanks very much,
> >>>
> >>> ~jimmy.
> >>
> >>
> >
>