cookie association with specific windows?

2011-05-19 Thread Mike Hobbs
In recent NS builds (past several months) I've noticed a
change in behaviour when logging in to our company bug
tracking system. At one time I could go through the
Login page and from then on I would be able to access
the whole bug tracking database through its web UI.
At some point that changed so that now,
 a) if I go through the normal Login process it fails
to accept my credentials;
 b) I have found that by going through an alternative URL
that throws up the Login page it results in success;
 c) even though I've logged in, when I open a new NS
window by clicking on a link that should open a
bug report (e.g. http://jira/browse/XXX-nnn), it
tells me I'm not logged in;
 d) if I enter the same URL as in c) above into the
window that was opened as per b) above, then it
displays the page without any trouble.

On the face of it, this looks like the cookie-stored
login status is associated only with the window that
was used for successful login.  Is this expected?
Do other people see similar behaviour? Should I file
a bug report?

I'm currently using the 2.7 release on VRPC-SA but this
affects earlier releases and development builds.

-- 
Mike Hobbs



Re: cookie association with specific windows?

2011-05-19 Thread Dave Lawton

On Thu, May 19, 2011 9:41 am, Mike Hobbs wrote:
> In recent NS builds (past several months) I've noticed a
> change in behaviour when logging in to our company bug
> tracking system. At one time I could go through the
> Login page and from then on I would be able to access
> the whole bug tracking database through its web UI.
> At some point that changed so that now,
>  a) if I go through the normal Login process it fails
> to accept my credentials;
>  b) I have found that by going through an alternative URL
> that throws up the Login page it results in success;
>  c) even though I've logged in, when I open a new NS
> window by clicking on a link that should open a
> bug report (e.g. http://jira/browse/XXX-nnn), it
> tells me I'm not logged in;
>  d) if I enter the same URL as in c) above into the
> window that was opened as per b) above, then it
> displays the page without any trouble.
>
> On the face of it, this looks like the cookie-stored
> login status is associated only with the window that
> was used for successful login.  Is this expected?
> Do other people see similar behaviour? Should I file
> a bug report?
>
> I'm currently using the 2.7 release on VRPC-SA but this
> affects earlier releases and development builds.

I'm seeing something similar (on 2.7), in that when I'm logged in to
my Orpheus webmail, if the session times out, then I can't login
again, I'm just taken back to the login page, with the message 'Your
session has timed out'.
Deleting the cookies (is the 'Are you sure' second delete an accident,
or intentional ?), and closing the window is not enough to restore
access, only quitting NetSurf completely will restore access.

Should I file a bug report ?  :)
-- 
Regards from Dave Lawton
HTML emails are just a security risk, and nobody needs that.




Google Groups

2011-05-19 Thread Harriet Bazley
Have they changed the Google Usenet archive interface so that it is no
longer possible to post to Usenet groups without Javascript?

I tried it via Firefox, and character entry was at so abysmally glacial
a rate that it's possible every single keypress was being processed via
a script (to strip end of line spaces perhaps?)

-- 
Harriet Bazley ==  Loyaulte me lie ==

Motorcar: a four-wheeled vehicle that runs up hills and down pedestrians



Re: Google Groups

2011-05-19 Thread Chris Newman
In article <7925d3d551.harr...@blueyonder.co.uk>,
   Harriet Bazley  wrote:
> Have they changed the Google Usenet archive interface so that it is no
> longer possible to post to Usenet groups without Javascript?

Something has changed. Using netsurf, I tried replying to a thread the other
day & got a message along the lines of... "Could not post your message. If
you think this is a fault contact Google Groups". I did & they have not
replied. Hey, ho.

-- 
Chris