Setting Authentication Using SetMimeHeader Tag

This WebDNA talk-list message is from

2004


It keeps the original formatting.
numero = 56091
interpreted = N
texte = Good day all, Case 1 Here is what I would like to do. I would like to set the Username and Password generated by a page hit automatically for the visitor, without the visitor having to handle "Authentication pop boxes". The username and password is generic, unique and generated by WebDNA and once set, can be referred to via the standard USERNAME / PASSWORD tags. Good to use only for the session, no need to "remember" it. Basically, it is like setting a cookie, totally transparent to the client, however, using authentication instead of a real cookie. Can the SetMimeHeader Tag be used to tell a client browser to store the Base64 encoded "BASIC username:password" for the site which then can be called upon during the session visit? If so, could someone please tell me how this can be done with the proper syntax using SETMIMEHEADER. An after thought, maybe a JS way of doing it ...will explore this as well. Case 2 Also, we have tags that can tell the IP address, browser type, etc of the client's browser. Is there any "unpublished" tags that can be used to identify a client's machine ...its MAC Address for example or any cross-platform data that uniquely identifies a machine behind a router. As we know, machines behind a NAT router will have unique LAN IP address but all will show the same WAN IP address when the "IP Address" tag is used. However, it will pass the correct identifier to the browser type, listmimeheader data etc. unique to the browser, behind the router except the IP Address. It is certainly a browser thingy so machine number may not be possible, but maybe a browser's unique id or something per machine installed that can be trapped and is available in the browser. Do forgive me if the questions above seems ridiculous. I am really searching for a solution like the "cookie" without having to resort to page to page token cart passing via the URL in a cookie-less & form-less environment. Any help or pointers would be much appreciated. Starting to think silly-willy ideas here in the hope that some smart person out there can put me out of my misery. Cheers TDn ------------------------------------------------------------- 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://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Setting Authentication Using SetMimeHeader Tag ( Terry Nair 2004)
Good day all, Case 1 Here is what I would like to do. I would like to set the Username and Password generated by a page hit automatically for the visitor, without the visitor having to handle "Authentication pop boxes". The username and password is generic, unique and generated by WebDNA and once set, can be referred to via the standard USERNAME / PASSWORD tags. Good to use only for the session, no need to "remember" it. Basically, it is like setting a cookie, totally transparent to the client, however, using authentication instead of a real cookie. Can the SetMimeHeader Tag be used to tell a client browser to store the Base64 encoded "BASIC username:password" for the site which then can be called upon during the session visit? If so, could someone please tell me how this can be done with the proper syntax using SETMIMEHEADER. An after thought, maybe a JS way of doing it ...will explore this as well. Case 2 Also, we have tags that can tell the IP address, browser type, etc of the client's browser. Is there any "unpublished" tags that can be used to identify a client's machine ...its MAC Address for example or any cross-platform data that uniquely identifies a machine behind a router. As we know, machines behind a NAT router will have unique LAN IP address but all will show the same WAN IP address when the "IP Address" tag is used. However, it will pass the correct identifier to the browser type, listmimeheader data etc. unique to the browser, behind the router except the IP Address. It is certainly a browser thingy so machine number may not be possible, but maybe a browser's unique id or something per machine installed that can be trapped and is available in the browser. Do forgive me if the questions above seems ridiculous. I am really searching for a solution like the "cookie" without having to resort to page to page token cart passing via the URL in a cookie-less & form-less environment. Any help or pointers would be much appreciated. Starting to think silly-willy ideas here in the hope that some smart person out there can put me out of my misery. Cheers TDn ------------------------------------------------------------- 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://webdna.smithmicro.com/ Terry Nair

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:

WebDNA permissions? (2002) is there a global includes directory? (1998) Stumpted Again (1997) all records returned. (1997) PROBLEM (1997) Date problems (1997) Search: Is this possible? (2005) Javascripts (1998) & in Lookups (1997) emailer w/F2 (1997) woops - speed results - right subject (2002) default value from Lookup (1997) FW: writefile and emailer (2002) XML WebDNA Problems (2000) All questions are welcome on this list (1997) Modifying order output (1997) [WriteFile] problems (1997) Sendmail Context (2003) Interactive Docs (2007) trouble updating records in database (1998)