MobileRead Forums - View Single Post - Keep logged-in state across browser restarts

Comfy.n · 12-17-2022, 01:14 AM

Hi,

I'm not used to keeping the Content Server always on, but recently i felt the need for this, as I found myself doing frequent full-text searches in my libraries from text selections while browsing the web.

Then I noticed that, after browser restarts, the password prompt will come up. Perhaps the need for re-authenticating to the CS has appeared also after some "idle" time, I mean, while CS tab is open but not being used; I'm not sure.

I see cookies from 127.0.0.1 are being set and have already whitelisted those to be kept across browser sessions, so I don't see the need for repeated logins, in my use case, which is local access only.

There's a timeout setting described as "Time (in seconds) after which an idle connection is closed." Does setting this to 0 (zero) mean that no timeout will happen? Is this setting relevant for this matter?

TL;DR - Is there a way to keep CS access permanently ready to access from the browser, without the need to provide user credentials?

12-17-2022, 01:14 AM	#1
Comfy.n want to learn what I want Posts: 1,639 Karma: 7908443 Join Date: Sep 2020 Device: none	Keep logged-in state across browser restarts Hi, I'm not used to keeping the Content Server always on, but recently i felt the need for this, as I found myself doing frequent full-text searches in my libraries from text selections while browsing the web. Then I noticed that, after browser restarts, the password prompt will come up. Perhaps the need for re-authenticating to the CS has appeared also after some "idle" time, I mean, while CS tab is open but not being used; I'm not sure. I see cookies from 127.0.0.1 are being set and have already whitelisted those to be kept across browser sessions, so I don't see the need for repeated logins, in my use case, which is local access only. There's a timeout setting described as "Time (in seconds) after which an idle connection is closed." Does setting this to 0 (zero) mean that no timeout will happen? Is this setting relevant for this matter? TL;DR - Is there a way to keep CS access permanently ready to access from the browser, without the need to provide user credentials? Last edited by Comfy.n; 12-21-2022 at 07:31 AM.