Re: [WebDNA] Internal [ipaddress] ?

This WebDNA talk-list message is from

2009


It keeps the original formatting.
numero = 102301
interpreted = N
texte = Dan, Don't know if this would help you, but we do something similar, but base it on a referrer, which could also be an ip address. On the index page we check for the validation cookie: ------------------------- [hideif [GETCOOKIE name=COOKIENAME]=VALIDATED]][REDIRECT url=validate.tpl][/hideif] [showif [GETCOOKIE name=COOKIENAME]=VALIDATED] ---------------- The validate.tpl contains: ---------------------------- [showif [REFERER]^mysite.com/global/StoreLink.jsp] [SETCOOKIE name=COOKIENAME&Value=VALIDATED&path=/] [REDIRECT url=index.tpl][/showif] [hideif [REFERER]^mysite.com/global/StoreLink.jsp]NOT AUTHORIZED[/ hideif] --------------------------- To login from outside that area we hit a login page containing: -------------------------- [protect USER] [SETCOOKIE name=COOKIENAME&Value=VALIDATED&path=/] [REDIRECT url=index.tpl][/showif] ------------------------- I think you could make it work by replacing the one line: [showif [REFERER]^mysite.com/global/StoreLink.jsp] with [showif [REFERER]^[ipaddress]] Just a thought.... Rob On 30-Mar-09, at 5:42 PM, Dan Strong wrote: > No prob, maybe I wasn't quite as clear as I should have been. I have > a site that needs to differentiate between external and internal > users, that's all. The site is an "intranet" site that employees are > allowed to view from home via a public facing URL, so I have to lock- > it down. If access is from within the network, though (like in the > Employee Dining Room or from someone's desk), I can assume they are > employees, otherwise they wouldn't have been able to log into the > corp. network, or gotten into the building to begin with. Since the > site is public-facing, IT obviously doesn't want to tie it to the > corporate Active Directory stuff, so I am trying to fake unified- > login by detecting internal users and simply foregoing log-in. I've > identified our public-facing IP range and can do it that way it > appears, but I was just wondering if I could identify internal > network IPs via WebDNA and if so how. > -Dan > Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Internal [ipaddress] ? (Stuart Tremain 2009)
  2. Re: [WebDNA] Internal [ipaddress] ? (Patrick McCormick 2009)
  3. Re: [WebDNA] Internal [ipaddress] ? ("Dan Strong" 2009)
  4. Re: [WebDNA] Internal [ipaddress] ? (Rob 2009)
  5. Re: [WebDNA] Internal [ipaddress] ? (Patrick McCormick 2009)
  6. Re: [WebDNA] Internal [ipaddress] ? ("Dan Strong" 2009)
  7. Re: [WebDNA] Internal [ipaddress] ? ("Dan Strong" 2009)
  8. Re: [WebDNA] Internal [ipaddress] ? (Stuart Tremain 2009)
  9. Re: [WebDNA] Internal [ipaddress] ? (Donovan Brooke 2009)
  10. Re: [WebDNA] Internal [ipaddress] ? ("Dan Strong" 2009)
  11. Re: [WebDNA] Internal [ipaddress] ? (Stuart Tremain 2009)
  12. [WebDNA] Internal [ipaddress] ? ("Dan Strong" 2009)
Dan, Don't know if this would help you, but we do something similar, but base it on a referrer, which could also be an ip address. On the index page we check for the validation cookie: ------------------------- [hideif [GETCOOKIE name=COOKIENAME]=VALIDATED]][REDIRECT url=validate.tpl][/hideif] [showif [GETCOOKIE name=COOKIENAME]=VALIDATED] ---------------- The validate.tpl contains: ---------------------------- [showif [REFERER]^mysite.com/global/StoreLink.jsp] [SETCOOKIE name=COOKIENAME&Value=VALIDATED&path=/] [REDIRECT url=index.tpl][/showif] [hideif [REFERER]^mysite.com/global/StoreLink.jsp]NOT AUTHORIZED[/ hideif] --------------------------- To login from outside that area we hit a login page containing: -------------------------- [protect USER] [SETCOOKIE name=COOKIENAME&Value=VALIDATED&path=/] [REDIRECT url=index.tpl][/showif] ------------------------- I think you could make it work by replacing the one line: [showif [REFERER]^mysite.com/global/StoreLink.jsp] with [showif [REFERER]^[ipaddress]] Just a thought.... Rob On 30-Mar-09, at 5:42 PM, Dan Strong wrote: > No prob, maybe I wasn't quite as clear as I should have been. I have > a site that needs to differentiate between external and internal > users, that's all. The site is an "intranet" site that employees are > allowed to view from home via a public facing URL, so I have to lock- > it down. If access is from within the network, though (like in the > Employee Dining Room or from someone's desk), I can assume they are > employees, otherwise they wouldn't have been able to log into the > corp. network, or gotten into the building to begin with. Since the > site is public-facing, IT obviously doesn't want to tie it to the > corporate Active Directory stuff, so I am trying to fake unified- > login by detecting internal users and simply foregoing log-in. I've > identified our public-facing IP range and can do it that way it > appears, but I was just wondering if I could identify internal > network IPs via WebDNA and if so how. > -Dan > Rob

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:

Support ?? (1997) 404 error -- but wc code executes... (2001) Trouble with formula.db (1997) [returnraw] and form variables (1998) WebCat2: Items xx to xx shown, etc. (1997) Monthly Help File (2000) [searchstring] (1998) Multiple prices (1997) Re:Searching for ALL / empty form field (1997) Printing from Web pages (1998) WebCatalog dying in WebTen (1998) [tcpsend] (2001) All choices on IE different than Netscape (1997) WC TableGrinder (1997) download a file (2001) Bug? (1997) Bad Cookie / Internet Option / Internet Explorer (2004) Preserving form data (1999) Store Builder, technical infos (1998) using webdna to determine pixel parameters (2000)