404 error after 30 min of inactivity?

GeoServer GeoServer User
1

Hi all,
After upgrading from GeoServer 2.4.8 to 2.26.1 (yes, a big leap!), I have noticed in my testing phase that I’m getting an HTTP Status 404 – Not Found error when I visit any GeoServer page after 30 minutes of inactivity in my GeoServer session. In the older 2.4.8 version, the interface would instead show a page that said:

Sorry, your session timed out…

It looks like you waited too long to make that last change.if this continues to happen, you should get in touch with your system administrator.

Go back to the home page and try again.

This was much more helpful, especially for end users who may not know how to proceed, and I’m hoping there’s a way to get that back in 2.26.1? My workaround for the 404 error is to remove everything after /geoserver/web/ in my URL and reload GeoServer to get it working again.

Has anybody else seen this HTTP 404 problem before? Is it something I might fix through a configuration setting? Or is it perhaps a bug?
Many thanks!,
John Maurer
Data System Engineer
Pacific Islands Ocean Observing System (PacIOOS)
University of Hawaii at Manoa

2

Hello @johnolulu and welcome to the user forum.

Checking the code that text stills exsists:

GeoServerExpiredPage.title            = Sorry, your session timed out...

And appears to be used:

getApplicationSettings().setPageExpiredErrorPage(GeoServerExpiredPage.class);

Reading online indicates that there is a difference between page expired (no longer cached) and session expired.

So it appears the page exists and is perhaps longer hooked up correctly. Are you in position to look into this and work on a pull request? We would love the assistance.

3

Thanks for your input, @jive! I’m happy to install new versions of GeoServer and/or test out any fixes that you can recommend for me to try on my end. Let me know how I can help!

4

Thanks,

If you do not wish this issue to get lost, please report it to our issue tracker.

Thanks also for the offer of assistance. Each release cycle we issue a release candidate, or ask for testing of nightly builds. The project really benefits from early-access testing and feedback. This is one of the best in-kind contributions you can make towards project sustainability. It is a quality assurance activity we can all share.

The other contributions we are looking towards is the GeoServer 3 Crowdfunding activity (if you wish to share with your organization).

5

Thanks a lot, @jive! I will use the issue tracker and keep an eye on the release cycle for testing. I will also pass along the crowdfunding page.

6

Sounds like Wicket changed behavior on us over the years… it it’s due to a HTTP session expiry,
the following may apply:

https://stackoverflow.com/questions/61457281/handle-session-time-out-with-wicket

Anyone wants to give it a try and make a PR?

1 Like
7

I have tried it with a new installation, and I don’t get a 404. Just the login page.
Regards,
Roar Brænden

8

Thanks for the info, @roarbra. I wonder if in upgrading from 2.4.8 to 2.26.1 that one of my pre-existing XML configs is out-dated and does not contain some new tag(s) for handling this?

I had a similar issue with the new option to “Support on the fly geometry simplification”. I discovered it was defaulting to simplify vectors because my Store config (datastore.xml) was old and did not yet have an XML entry for this new feature: <entry key="Support on the fly geometry simplification">. Once I clicked Save on the Edit Vector Data Source page, it updated my underlying datastore.xml to include this new config as false and solved the problem.

I wonder if there is something similar going on since it seems to work with a fresh installation (@roarbra) as opposed to an upgrade like mine?

9

That is a thought, there is a settings on the admin screen about where to redirect people when logged out.

Perhaps you have an older / odd default value?

  1. Security > Authentication Page
  2. Logout settings, the Redirect URL after logout: /web/
  3. See security/filter/formLogout/config.xml
10

Thanks for the idea, @jive. I can confirm that mine is also /web/, both in the admin settings and in my formLogout/config.xml. So, that doesn’t seem to be it.

However, I see a bunch of Filter Chains on my Security > Authentication page that I don’t understand. Do you happen to know if these are typical/default, or possibly the cause of my 404 error?

geoserver_filterchains
geoserver_filterchains1846×684 83.3 KB

11

You can always copy and remove your security folder and geoserver will make a new one again. Be sure to follow the warnings and turn on digest etc… just like a fresh install.

If the result does not fix it you can restore your previous folder etc…