kanwisch has asked for the wisdom of the Perl Monks concerning the following question:

I've spent the better part of three days figuring out why our dev server, with exactly the same Perl installation and IIS configuration (or so the admins tell me), can pass a cookie to my 5.50 IE, but our production system couldn't.

The final solution was that if I removed my spec of the domain, all was well in production. So, how might that be? Is this likely an IIS problem, as opposed to the module? I sort of lean this direction since everything appears to work fine on the dev server, but both are running IIS 4.0 on NT4.0 SP6a. Patches are applied on both machines equally. Ain't M$ grand?

Writer takes no responsibility for ranting as a result of this content.

  • Comment on Does IIS and CGI::cookie have domain incompatibilities?

Replies are listed 'Best First'.
(crazyinsomniac) Re: Does IIS and CGI::cookie have domain incompatibilities?
by crazyinsomniac (Prior) on Dec 20, 2001 at 11:26 UTC
    I am not aware of any issues (but then again, I'm not that aware).

    What does "removed my spec of the domain" mean? Why would that fix the problem?

    I suspect that the domain name is morphing between the cookie and the actual url.

    Frankly, this question is more than sufficiently vague, and as such, I will stop typing soon(If you spent 3 days figuring it out, and you've seen the code, what chance do we, the perlmonks, have of enven guessing, without having more than an pin point worth of an inkling of what you're doing).


    crazyinsomniacs advice for the week (now part of my signature): Week of December 19, 2001
    I say .. listen to me boy, I say, everybody needs to read the following, it's good infodvice: How to RTFM, On asking for help, and Don't just provide a module name.

     
    ___crazyinsomniac_______________________________________
    Disclaimer: Don't blame. It came from inside the void

    perl -e "$q=$_;map({chr unpack qq;H*;,$_}split(q;;,q*H*));print;$q/$q;"