| Re: setcookie() Expiration [message #171074 is a reply to message #171073] |
Wed, 22 December 2010 22:31  |
Tyrone Slothrop
Messages: 3
Registered: December 2010
Karma:
|
Junior Member |
|
|
On Wed, 22 Dec 2010 18:09:03 +0100, "Álvaro G. Vicario"
<alvaro(dot)NOSPAMTHANX(at)demogracia(dot)com(dot)invalid> wrote:
> El 22/12/2010 17:02, Tyrone Slothrop escribió/wrote:
>>> The first step is to inspect the output of setcookie(). You can see the
>>> raw HTTP header with many tools, such as the Firebug extension for
>>> Firefox, but most browsers have a builtin cookie manager as well.
>>>
>>> Also, make sure you are using a valid domain name for your tests.
>>
>> Let's assume that I pretty much know what I am doing. I have been
>> coding PHP for at least 12 years, developing backends for complex web
>> sites. Not to say I don't make mistakes - and I make some incredibly
>> silly ones at times - but I have verified the code on a different
>> server and I know it works.
>
> I apologize if my suggestions have hurt your feelings. I understand that
> a PHP coder with 12 years of experience does not need to see the
> Set-Cookie header or the information provided by the browser's cookie
> manager but I didn't know it was the case.
>
> Come on, take a deep breath and relax. Obvious issues are sometimes the
> most difficult to find. You wouldn't be the first one to have HTTP
> headers mangled by a server module, firewall, antivirus or browser
> extension.
No offense taken. The discussions in this group are far more gentle
compared to the flames I have received in the CSS group. ;-)
Ironically, I tried on another computer and my laptop with the same
version of FF with the same extensions (all on Win7-64) and the
cookies were set with proper expiration. Then I had the client try it
but the cookies were not set with expiration in FF on Vista-64, but
did work in IE.
I cannot isolate the common thread which would cause the problem so
decided to go with another method of validation to work in parallel
so, should the cookies fail, there is a backup system. I much prefer
server side solutions rather than having to rely upon the whims of
browsers anyway. However, clients demand the features they see on
other sites so JS and AJAX are necessary tools. The form that this
processing script leads into has close to 4000 lines of hybrid HTML,
DHTML, PHP, JS, AJAX and SOAP that took weeks to develop and debug.
They asked why I bang my head against the wall? I replied, it feels
so good when I stop.
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]