[Catalyst] Manipulating CGI cookie via Catalyst

[sindharta_tanuwijaya at yahoo.co.jp]

Hi,

I am not sure if I should continue this thread, but please let me report.
If what you are saying, different ports is treated as different domains, is correct, then modifying the cookie by Javascript will also fail, won't it ?
In my case though, modifying the cookies by Javascript works. This is the JS code.

<script type="text/javascript">
// this deletes the cookie when called
function logout( ) {
  document.cookie = 'id' + "=ab" + ";domain=.sin.my.office.com"  + ";path=/" +";expires=Thu, 01-Jan-1970 00:00:01 GMT";
  document.cookie = 'session' + "=asdf" + ";domain=.sin.my.office.com"  + ";path=/" + ";expires=Thu, 01-Jan-1970 00:00:01 GMT";
}
logout( );
</script>

I accessed the Javascript on http://sin.my.office.com:3000 (added it into the template), and the apache is still on http://sin.my.office.com (that's port 80, the default)

So does it mean that Javascript will regard different ports on the same domains as having the same domains while Catalyst apps will treat different ports as different domains ?

Sindharta

sindharta_tanuwijaya at yahoo.co.jp wrote: Whoops ! Sorry for that. So it's the port ??
 Thank you for the hints there. I think I should start reading HTTP cookie wiki then.
 Thanks again.
 
 Siindharta
 
 Adam Clarke <adam.clarke at strategicdata.com.au> wrote: On 03/06/2008, at 12:05 PM,  
  > wrote:
 
 > Yes, I was hoping that I've made a mistake there, but the thing is,  
 > I set up Apache in my computer so that I can access the PHP code on
 >
 > sin.my.office.com:80/login.php
 > while the catalyst works on sin.my.office.com:3000
 >
 > So there should be only one domain there, right ?
 
 As the previous poster noted, the different ports (80 vs 3000) result  
 in these being treated as different domains.
 
 You may want to re-read this message: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/msg03287.html
 
 You might like to try setting up your Apache such that http://sin.my.office.com/php/login.php 
   is directed to you PHP app and http://sin.my.office.com/ is handled  
 by your catalyst app. If you need help on setting that up, an apache  
 mailing list is probably the place.
 
 
 
 _______________________________________________
 List: Catalyst at lists.scsys.co.uk
 Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
 Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
 Dev site: http://dev.catalyst.perl.org/
 
   
    

---------------------------------
Power up the Internet with Yahoo! Toolbar.
 _______________________________________________
List: Catalyst at lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/

 

 
---------------------------------
Power up the Internet with Yahoo! Toolbar.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.scsys.co.uk/pipermail/catalyst/attachments/20080603/e7b0b924/attachment.htm