Re: Username/Password with [Protect]
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 35349
interpreted = N
texte = That information is cached by the web browser. Once the user enters their information then the browser should cache and resend when asked by the server. I would suggest using cookies (umm cookies) to authenticate your users after they logon the first time.Gary is correct that is the way Web Catalog should function.Does the same thing happen when using tpl pages?James Howarth ********************************** Smith Micro, Internet Solutions Div | eCommerce (WebCatalog) 16855 West Bernardo Drive | Software & Site Development Suite 380 | San Diego, CA 92127 | 858.675.1106 | http://www.smithmicro.com/isd 858.675.0372 (fax)-----Original Message----- From: WebCatalog Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of Kim Ingram Sent: Friday, July 28, 2000 8:06 AM To: WebCatalog Talk Subject: Re: Username/Password with [Protect] Not with my WebCatalog. I went back to template1.html and removed the username:password thing...changed it to a simple
click here...still having [protect cscc] on template2.html...the visitor is asked for a username and password again. (same as template1.html) > -----Original Message----- > From: WebCatalog Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On > Behalf Of Gary Krockover > Sent: Friday, July 28, 2000 10:44 AM > To: WebCatalog Talk > Subject: Re: Username/Password with [Protect] > > > Once a visitor logs in as user cscc, aren't they granted access > to all pages > that have [protect cscc], thus no need to put '[username]:[password]@' in > the href? > > Gary > > ----- Original Message ----- > From: Kim Ingram
> To: WebCatalog Talk > Sent: Friday, July 28, 2000 8:31 AM > Subject: Username/Password with [Protect] > > > > I'm not quite sure how this works. > > > > I have template1.html and template2.html. I want both to be [protect > cscc] > > > > So in template1.html, I have the following: > > > > [protect cscc] > > > > The visitor is asked for a username and password of course. The visitor > > enters that information, and is granted access to view template1.html. > Also > > in Template1.html, I have the following: > > > > > > href=http://[username]:[password]@www.domain.com/folder/template2 > .html?comm > > and=newcart>Click Here > > > > In template2.html, I have the following: > > > > [protect cscc] > > > > The visitor is again asked for a username and password... > > > > I thought that the [username]:[password]@whatever would keep that from > > happening. I don't want the username and password to be passed > visibly in > > the URL (template2.html?command=newcart&username=[username]...) > > > > What am I doing wrong? > > > > > > > > ------------------------------------------------------------- > > This message is sent to you because you are subscribed to > > the mailing list . > > To unsubscribe, E-mail to: > > To switch to the DIGEST mode, E-mail to > > > Web Archive of this list is at: http://search.smithmicro.com/ > > > > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > > Web Archive of this list is at: http://search.smithmicro.com/ > > ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
That information is cached by the web browser. Once the user enters their information then the browser should cache and resend when asked by the server. I would suggest using cookies (umm cookies) to authenticate your users after they logon the first time.Gary is correct that is the way Web Catalog should function.Does the same thing happen when using tpl pages?James Howarth ********************************** Smith Micro, Internet Solutions Div | eCommerce (WebCatalog) 16855 West Bernardo Drive | Software & Site Development Suite 380 | San Diego, CA 92127 | 858.675.1106 | http://www.smithmicro.com/isd 858.675.0372 (fax)-----Original Message----- From: WebCatalog Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of Kim Ingram Sent: Friday, July 28, 2000 8:06 AM To: WebCatalog Talk Subject: Re: Username/Password with [protect] Not with my WebCatalog. I went back to template1.html and removed the username:password thing...changed it to a simple click here...still having [protect cscc] on template2.html...the visitor is asked for a username and password again. (same as template1.html) > -----Original Message----- > From: WebCatalog Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On > Behalf Of Gary Krockover > Sent: Friday, July 28, 2000 10:44 AM > To: WebCatalog Talk > Subject: Re: Username/Password with [protect] > > > Once a visitor logs in as user cscc, aren't they granted access > to all pages > that have [protect cscc], thus no need to put '[username]:[password]@' in > the href? > > Gary > > ----- Original Message ----- > From: Kim Ingram > To: WebCatalog Talk > Sent: Friday, July 28, 2000 8:31 AM > Subject: Username/Password with [protect] > > > > I'm not quite sure how this works. > > > > I have template1.html and template2.html. I want both to be [protect > cscc] > > > > So in template1.html, I have the following: > > > > [protect cscc] > > > > The visitor is asked for a username and password of course. The visitor > > enters that information, and is granted access to view template1.html. > Also > > in Template1.html, I have the following: > > > > > > href=http://[username]:[password]@www.domain.com/folder/template2 > .html?comm > > and=newcart>Click Here > > > > In template2.html, I have the following: > > > > [protect cscc] > > > > The visitor is again asked for a username and password... > > > > I thought that the [username]:[password]@whatever would keep that from > > happening. I don't want the username and password to be passed > visibly in > > the URL (template2.html?command=newcart&username=[username]...) > > > > What am I doing wrong? > > > > > > > > ------------------------------------------------------------- > > This message is sent to you because you are subscribed to > > the mailing list . > > To unsubscribe, E-mail to: > > To switch to the DIGEST mode, E-mail to > > > Web Archive of this list is at: http://search.smithmicro.com/ > > > > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > > Web Archive of this list is at: http://search.smithmicro.com/ > > ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
James Howarth
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Webcat run amuk (2002)
TaxTotal (2003)
Custom Convertchars Database (2004)
Passing Variable (was How to add product size) (1997)
case sensitivity in lookups (1997)
test (2005)
Custom Shipping Charges (1997)
format problem on NT? (1997)
Help name our technology! (1997)
Credit Card Number checking (1997)
Waitfor(ever) (2002)
Encryption of E-mail (1998)
Version 4? (2000)
[WebDNA] [OT] File structure for purchased downloads (2010)
Automatic installation of WebDNA by hosting clients? (2005)
Frames and WebCat (1997)
[WebDNA] Major grep/convertchars linux issues when writing to db (2010)
Protect vs Authenicate (1997)
WebCatalog can't find database (1997)
WebCatalog and directory indexing (1998)