 | | | | | |
Hi all,
luckily I am using Macs myself - unfortunately I didn’t notice this issue since
I personally prefer Firefox over Safari on Mac OS X.
Anyway, I tried everything myself and narrowed the issue down to the primary
cookie being created - the cookie name being used in LUGNET apparently is not
very much to Safari’s liking, however since cookie naming is embedded deeply in
the code, this is not changed easily.
I will try to change the name of the login cookie to a name that will be
accepted by Safari. I will update you when things are fixed. In the meantime,
your best bet would be Firefox which I have found is a very useful piece of
software on all operating systems.
Regards,
Jerry
| | | | | | | | | | | | | | |
In lugnet.admin.general, Gereon Stein wrote:
| |
Hi all,
luckily I am using Macs myself - unfortunately I didn’t notice this issue
since I personally prefer Firefox over Safari on Mac OS X.
Anyway, I tried everything myself and narrowed the issue down to the primary
cookie being created - the cookie name being used in LUGNET apparently is not
very much to Safari’s liking, however since cookie naming is embedded deeply
in the code, this is not changed easily.
I will try to change the name of the login cookie to a name that will be
accepted by Safari. I will update you when things are fixed. In the meantime,
your best bet would be Firefox which I have found is a very useful piece of
software on all operating systems.
Regards,
Jerry
|
I too ran into this same problem. I was unable to login to lugnet using Safari
3, but can login successfully using Firefox 3.
I was able to login in the past with Safari 2 with no problems.
Might this be a bug in webkit ?
Ray
| | | | | | |
