|
|
Home /
Groups /
ColdFusion Talk (CF-Talk)
IE6 Not Accepting Cookies From A Firewalled Web Site
I'm configuring a new server for a client. It is behind a firewall withPeter Lakanen 05/10/05 12:22 P > I'm guessing the issue is tied to the internal IP that IIS isDave Watts 05/10/05 01:33 P Problem solved.Peter Lakanen 05/10/05 06:07 P
Author: Peter Lakanen
I'm configuring a new server for a client. It is behind a firewall with both internal and external IP addresses. The server hosts two web sites, one written by me in ColdFusion, the other a legacy app originally written in ASP that I have to support. Both web sites use cookies. On the new server, neither of the web sites are working when I login using IE6. Both of them work just fine with Firefox. What I mean by this is that when using IE6, the browser does not appear to be accepting the cookies at all. I have added the sites to the Trusted Sites in both Security and Privacy. I have lowered all Privacy settings in IE6 to accept all cookies, but to no avail. I have added the DOMAIN parameter to CFCOOKIE in the CF app, but it still doesn't work. I'm guessing the issue is tied to the internal IP that IIS is configured for versus the external IP that IE6 sees. Anyone know how to solve this? If it involves any code changes, both the ColdFusion and the ASP code would be appreciated. I get this list in digest form, so if you have a solution for me, I would appreciate it if you could copy me directly on your post to the list so I don't have to wait 6 hours to see it. Thanks! -peter -- Peter Lakanen lakanen@platinumweb.com Platinum Web Development http://www.platinumweb.com 1320 Terrace Street Tallahassee, FL 32303 850.508.4518 FAX: 850.681.1930
Author: Dave Watts
> I'm guessing the issue is tied to the internal IP that IIS is > configured for versus the external IP that IE6 sees. That should make absolutely no difference at all. Cookies are associated with hosts and domains, not with IP addresses (assuming that you reached the server via a hostname and not an IP address typed into your browser's location bar). With this, as with so many other HTTP issues, being able to look at the raw HTTP requests and responses can be useful. You might try using a recording proxy or packet sniffer, or you might install something like ieHTTPHeaders: http://www.blunck.info/iehttpheaders.html Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information!
Author: Peter Lakanen
Problem solved. I used that ieHTTPHeaders tool Dave suggested and along with a couple friends we figured out the date/time stamp was wrong. This is a new server I am configuring (the client installed the OS and basic stuff) and it never occurred to me to check the date/time stamp, but it was three months and one hour behind! Once the clock/date was correctly set, the cookie problem went away. Thanks to everyone who offered advice on this problem. -peter -- Peter Lakanen lakanen@platinumweb.com Platinum Web Development http://www.platinumweb.com 1320 Terrace Street Tallahassee, FL 32303 850.508.4518 FAX: 850.681.1930
|
Mailing Lists
|
Latest Fusion Authority Articles
|
||||||
