Hey, it worked !!
I am not really sure, I think I've tried setting the domain before but it
didn't work at that time, but I've never set the path before so perhaps that
was the problem.
Anyway, yeah, just as you said, it's better to read the documentation more
patiently next time before bumping
On Mon, Jun 2, 2008 at 11:54 PM, <[EMAIL PROTECTED]> wrote:
> 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 ?
Cookies are not different depending on the programming
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
On Tue, Jun 3, 2008 at 3:05 AM, <[EMAIL PROTECTED]> wrote:
> Hi,
>
> 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
>
>
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 <[EMAIL PROTECTED]> wrote: On 03/06/2008, at 12:05 PM,
> wrote:
> Yes, I was hoping that I've made a mistake there, but the t
On 03/06/2008, at 12:05 PM, <[EMAIL PROTECTED]> <[EMAIL PROTECTED]
> 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:300
Hi,
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 ?
This is the HTTP respo
> I can delete the cookie which was previously set by the Catalyst app
> (testcookie), but I still can't delete the cookie which was previously set
> by the PHP. This is the PHP code:
> I tried to add
> $c->response->cookies->{id} = {
> value => [],
> expires => time-86400,
>
Give us the HTTP responses.
On Mon, Jun 2, 2008 at 2:56 AM, <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I can delete the cookie which was previously set by the Catalyst app
> (testcookie), but I still can't delete the cookie which was previously set
> by the PHP. This is the PHP code:
>
> setcookie("id
Hi,
I can delete the cookie which was previously set by the Catalyst app
(testcookie), but I still can't delete the cookie which was previously set by
the PHP. This is the PHP code:
I tried to add
$c->response->cookies->{id} = {
value => [],
expires => time-86400,
};
Hi Jackson,
Thanks for the source code. I'll be away from my workplace for a few days, but
I think I'll be back next week, so I'll try your source code and compare it
with mine at that time.
I'll let you know how it works.
Thanks again.
Sindharta
Mitch Jackson <[EMAIL PROTECTED]> wrote: Sindha
Sindharta,
I created a simple test application to set and delete a cookie, and it
is working as expected. The correct thing is happening in your
headers: as you roll back the expire time, that is reflected in the
headers that get sent.
I've posted my test application here:
http://perimus.com/fil
Thank you for your response. But I am still having the same problem if I don't
use Javascript.
I added:
$c->delete_session('Logout'); in Root/default
$c->res->cookies
->{id} = {
value => [],
expires => time()-86400,
};
$c->res->cookies
You need to understand how Cookies are writed.
Thery are HTTP Headers, so you may be giving an outdated value and
next the system gives a update value. Javascript writes the Cookies
after HTTP process, so the system values are irrelevant to it.
Try to use the Catalyst structure to manipulate them
14 matches
Mail list logo
