|
 |
asp_web_howto thread: Passing a variable throughout the site
Message #1 by "Mark Collins" <mark.collins@c...> on Tue, 27 Feb 2001 16:54:39
|
|
Hi all,
I need to be able to have a variable that is input at the login page to be
passed throughout the whole web site. In most appropriate pages on the
site I load an include file.
When first logging on to the site, the default.asp kicks in and redirects
to the login.asp site, the user logs in and then the login username and
password are sent to a verify.asp file, which then verifies that the user
is acceptable. The verify.asp file will then (if ok) redirect to
default.asp where browsing takes place etc, etc...
What I need to do is extract the username and password, send them to the
include file and then be able to use this information to give full or
restricted access to various users.
I think I should do this using an include file so that I don't have to
adjust all pages of the site.
There was an article some time ago on passing a variable throughout, but I
never read it because I had no need for this, but now I do.
Can anybody help
Thanks
Mark.
Message #2 by "Alex Shiell, ITS, EC, SE" <alex.shiell@s...> on Tue, 27 Feb 2001 17:11:59 -0000
|
|
2 options are
use the session object (unless the application need to be scalable across
multiple servers, this is the best)
use a cookie (browser might not accept cookies)
Message #3 by "Mark Collins" <mark.collins@c...> on Wed, 28 Feb 2001 21:43:02
|
|
Hi Alex,
Thanks for the response, I'm a newbie as I'm sure you can tell.
I would like to use the session object as I feel it would be the easiest
option, but I want to upload my site to brinkster.com, and unless I have
the wrong idea, they don't allow use of the session object.
The cookie choice could also work, but as you say browser may not accept.
would it not be possible to use FSO to write a text file on the client
storing the user/pass. I'm probably way off mark there, but I need a way
of storing variables somehow
Regards
Mark.
> 2 options are
>
> use the session object (unless the application need to be scalable across
> multiple servers, this is the best)
>
> use a cookie (browser might not accept cookies)
>
|
|
 |