passing information between ASPX pages

[francois]

I would like to pass information between ASPX pages.

For now, my navigation are hardcoded links.
In some case I do a Response.Redire ct("pages.aspx" )

Now I wonder is this is a good way to do.

For exemple when I log out of my website, i go back to the logon page but I
would like to write on the logon page something like "you succesfully logged
out".
Doing the following does not work :
Response.Write( "Sucessfull y Logged out!");
Response.Redire ct("Logon.aspx" );
(I assume a new Response objet is created when i redirect, right?)

Then should I do something like
Response.Redire ct("Logon.aspx? message='Sucess fully Logged out!'");

But this may lead in problems and string encoding (as my websites would use
many languages including chinese and japanese)

Then how is the proper, (state of the art :p) way to achieve my goal?

Thanks

Francois

[Curt_C [MVP]]

Well.... this:
Response.Write( "Sucessfull y Logged out!");
Response.Redire ct("Logon.aspx" );
does work...it jsut doesn't have time to send it to the browser.
You can pass the message with a URLEncode() to make sure it's not going to
break the URL

--
Curt Christianson
Owner/Lead Developer, DF-Software
www.Darkfalz.com
"francois" <fr******@betti nghouses.com_NO SPAM> wrote in message
news:%2******** ********@TK2MSF TNGP11.phx.gbl. ..

I would like to pass information between ASPX pages.

For now, my navigation are hardcoded links.
In some case I do a Response.Redire ct("pages.aspx" )

Now I wonder is this is a good way to do.

For exemple when I log out of my website, i go back to the logon page but I would like to write on the logon page something like "you succesfully logged out".
Doing the following does not work :
Response.Write( "Sucessfull y Logged out!");
Response.Redire ct("Logon.aspx" );
(I assume a new Response objet is created when i redirect, right?)

Then should I do something like
Response.Redire ct("Logon.aspx? message='Sucess fully Logged out!'");

But this may lead in problems and string encoding (as my websites would use many languages including chinese and japanese)

Then how is the proper, (state of the art :p) way to achieve my goal?

Thanks

Francois

[Michelle Stone]

As you put it, i don't know if this is the "state of the
art" way. But if you have reasons not to use
Response.Redire ct (a.aspx?message =hello); (QueryString[]
i mean), then why not use Session Variables?

Session Variables will work with any language you may
want.

Let me know if this is what you wanted

Regards,

Michelle

-----Original Message-----
I would like to pass information between ASPX pages.

For now, my navigation are hardcoded links.
In some case I do a Response.Redire ct("pages.aspx" )

Now I wonder is this is a good way to do.

For exemple when I log out of my website, i go back to the logon page but Iwould like to write on the logon page something like "you succesfully loggedout".
Doing the following does not work :
Response.Write ("Sucessfull y Logged out!");
Response.Redir ect("Logon.aspx ");
(I assume a new Response objet is created when i redirect, right?)
Then should I do something like
Response.Redir ect("Logon.aspx ?message='Suces sfully Logged out!'");
But this may lead in problems and string encoding (as my websites would usemany languages including chinese and japanese)

Then how is the proper, (state of the art :p) way to achieve my goal?
Thanks

Francois
.

[George Birbilis]

> Well.... this:

Response.Write( "Sucessfull y Logged out!");
Response.Redire ct("Logon.aspx" );
does work...it jsut doesn't have time to send it to the browser.
You can pass the message with a URLEncode() to make sure it's not going to
break the URL

avoid having pages of the form:
someURL?message =text

cause other people can exploit it (say from spam e-mails) to show any text
to users as if your site was showing it (they just make the appropriate URL
and send a page/e-mail with such a link to an unsuspected user saying you
sent it). Even MCAfee had such silly URLs some time ago, not sure if they
fixed them, at least I gave them a warning

Use session variables instead - log off the user when the login page is
(re)visited (if you see the user already has some name variable that isn't
equal to null/nothing at the session they were in so log them out and say
goodbye with their name, else don't do anything). To log off just do a
redirection to the login page then which will log the user out and before
logging them out will get their name from the session data and display the
goodbye message etc.

~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~ ~~~~
George Birbilis <bi******@kagi. com>
~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~ ~~~~
+ QuickTime VCL and ActiveX controls (for PowerPoint/VB/Delphi etc.)
+ Plugs VCL and ActiveX controls (InterProcess/Internet communication)
+ TransFormations , VB6 forms to ASP.net WebForms convertion
http://www.kagi.com/birbilis
+ Robotics
http://www.mech.upatras.gr/~robgroup
............... ............... ............... ............... .............

[Curt_C [MVP]]

Not always. Sessions are not always the way either. I would however encode
the URL, or rather encrypt it.... for less threat of a hack attack...

--
Curt Christianson
Owner/Lead Developer, DF-Software
www.Darkfalz.com
"George Birbilis" <bi******@kagi. com> wrote in message
news:O9******** ******@TK2MSFTN GP09.phx.gbl...

Well.... this:
Response.Write( "Sucessfull y Logged out!");
Response.Redire ct("Logon.aspx" );
does work...it jsut doesn't have time to send it to the browser.
You can pass the message with a URLEncode() to make sure it's not going to break the URL
avoid having pages of the form:
someURL?message =text

cause other people can exploit it (say from spam e-mails) to show any text
to users as if your site was showing it (they just make the appropriate

URL and send a page/e-mail with such a link to an unsuspected user saying you
sent it). Even MCAfee had such silly URLs some time ago, not sure if they
fixed them, at least I gave them a warning

Use session variables instead - log off the user when the login page is
(re)visited (if you see the user already has some name variable that isn't
equal to null/nothing at the session they were in so log them out and say
goodbye with their name, else don't do anything). To log off just do a
redirection to the login page then which will log the user out and before
logging them out will get their name from the session data and display the
goodbye message etc.

~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~ ~~~~
George Birbilis <bi******@kagi. com>
~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~ ~~~~
+ QuickTime VCL and ActiveX controls (for PowerPoint/VB/Delphi etc.)
+ Plugs VCL and ActiveX controls (InterProcess/Internet communication)
+ TransFormations , VB6 forms to ASP.net WebForms convertion
http://www.kagi.com/birbilis
+ Robotics
http://www.mech.upatras.gr/~robgroup
............... ............... ............... ............... ............

[RAMADU]

-----Original Message-----
I would like to pass information between ASPX pages.

For now, my navigation are hardcoded links.
In some case I do a Response.Redire ct("pages.aspx" )

Now I wonder is this is a good way to do.

For exemple when I log out of my website, i go back to the logon page but Iwould like to write on the logon page something like "you succesfully loggedout".
Doing the following does not work :
Response.Write ("Sucessfull y Logged out!");
Response.Redir ect("Logon.aspx ");
(I assume a new Response objet is created when i redirect, right?)
Then should I do something like
Response.Redir ect("Logon.aspx ?message='Suces sfully Logged out!'");
But this may lead in problems and string encoding (as my websites would usemany languages including chinese and japanese)

Then how is the proper, (state of the art :p) way to achieve my goal?
Thanks

Francois

Hi Francois,

What you could do is to have a variable in the session
which will check if the user is logging out or if the user
is logging in for the first time. While loading the page,
you can check if the session variable exists or not. If it
does exist, then you can display the appropriate logout
message. Else, you don't have to display any message.
Regards,

RAMADU