Re: how to make Netsurf forget its logged-in state

[Harriet Bazley]

On 12 May 2016 as I do recall,
  Jim Nagel  wrote:

> I'm tinkering with something on my own website, an area that requires
> the viewer to provide a username and password.
>
> I successfully get in with my own username and password.  Now I want
> to test those of another user.
>
> So I click the link that takes me to the subsite -- and I'm straight
> in; I don't see any box asking for username and password.
>
> Tried Ctrl-F5, menu Reload, tried deleting from the History file,
> tried quitting and relaunching Netsurf.  Still never see the login box
> again.
>
> How do I "log out"?  (If that's the correct term in this situation.
> Maybe it's more like changing the "state".)
>

Clearing the cache/cookie file?

(This worked for me in a remote site where the 'logout' link didn't function
with Netsurf, but then the site was setting cookies to store log-in status.)

-- 
Harriet Bazley ==  Loyaulte me lie ==

We prefer to speak evil of ourselves than not speak of ourselves at all.

how to make Netsurf forget its logged-in state

[Jim Nagel]

I'm tinkering with something on my own website, an area that requires 
the viewer to provide a username and password.

I successfully get in with my own username and password.  Now I want 
to test those of another user.

So I click the link that takes me to the subsite -- and I'm straight 
in; I don't see any box asking for username and password.

Tried Ctrl-F5, menu Reload, tried deleting from the History file, 
tried quitting and relaunching Netsurf.  Still never see the login box 
again.

How do I "log out"?  (If that's the correct term in this situation.  
Maybe it's more like changing the "state".)

-- 
Jim Nagelwww.archivemag.co.uk

Re: Slow ?

[Peter Slegg]

On Wed, 11 May 2016 13:30:33 , Vincent Sanders  
wrote:
> As I have mentioned previously, the Atari port has no active
> maintainer and therefore only receives the absolute minimum of changes
> to keep it compiling in the CI system. This is also why it is not a
> release candidate frontend.
>
> Given the general lack of developer time at present I cannot guarantee
> there will be resources to examine this issue.
>
> On Tue, May 10, 2016 at 09:27:54PM +, Peter Slegg wrote:
> >
> > In the past few weeks I've noticed that the download and
> > rendering speed of the (Atari) test builds seems quite a
> > bit slower than with earlier versions.
>
> As far as I know there have been no core changes recently that would
> affect the browsers speed. Generally all recent changes have been code
> cleanups in preparation for larger planned updates.
>
> Please can I ask you to check that you have not made any other changes
> to your system that might have caused this. There have been several
> reports recently which have turned out to be related to updates
> completely unrelated to NetSurf.
>
> >
> > Some pages are taking over 20 mins and more are timing out.
>
> Perhaps you can provide the CI build numbers of "working" and "slow"
> versions? the closer these values are together the easier it will be
> for a developer to attempt to diagnose the issue.
>
> >
> >
> > Peter
> >
> >

Since the Atari is one of the slower machines using Netsurf I
imagine it is good test for highlighting anything reducing speed.
High-end users might not notice a small speed drop.

I am going to work back through the versions to see if it is a real
or imagined performance drop.

I haven't made any changes that could have affected the performance.

Regards,

Peter

Re: Slow ?

[Vincent Sanders]

As I have mentioned previously, the Atari port has no active
maintainer and therefore only receives the absolute minimum of changes
to keep it compiling in the CI system. This is also why it is not a
release candidate frontend.

Given the general lack of developer time at present I cannot guarantee
there will be resources to examine this issue.

On Tue, May 10, 2016 at 09:27:54PM +, Peter Slegg wrote:
> 
> In the past few weeks I've noticed that the download and
> rendering speed of the (Atari) test builds seems quite a
> bit slower than with earlier versions.

As far as I know there have been no core changes recently that would
affect the browsers speed. Generally all recent changes have been code
cleanups in preparation for larger planned updates.

Please can I ask you to check that you have not made any other changes
to your system that might have caused this. There have been several
reports recently which have turned out to be related to updates
completely unrelated to NetSurf.

> 
> Some pages are taking over 20 mins and more are timing out.

Perhaps you can provide the CI build numbers of "working" and "slow"
versions? the closer these values are together the easier it will be
for a developer to attempt to diagnose the issue.

> 
> 
> Peter
> 
> 
> 
> 
> 
> 

-- 
Regards Vincent
http://www.kyllikki.org/