yes sounds good, since it's in the docs with "status" just add the mapping to the ServerStatusServlet for now to be in line with the documentation and to reduce developer frustration.
long term we can possibly introduce a more specialized server servlet for additional admin server monitoring. On Fri, Nov 23, 2018 at 12:07 PM Andy Seaborne <[email protected]> wrote: > Thanks Marco. > > It seems to be mapped /$/server and AFAICS has not been mapped to > /$/status., only mentioned in shiro.ini. > > Easy enough to add a second servlet-mapping if that's what people want > (the difference is that by default, /$/status is acess to anon and > /$/server is accessible only to the admin UI). > > Thoughts? > > Andy > > On 23/11/2018 11:10, Marco Neumann wrote: > > just went back to 3.4 and it did not work. now upgraded to 3.9 to no > avail > > of status. > > > > > /$/stats works well though > > > > since there is no action URL mapping in the web.xml for status I presume > > that /$/status = anon is a typo in shiro. > > > > > > > > On Thu, Nov 22, 2018 at 11:44 PM Andy Seaborne <[email protected]> wrote: > > > >> Do you happen to know in which version it last did work? > >> > >> Andy > >> > >> On 22/11/2018 23:23, Marco Neumann wrote: > >>> while you are at the fuseki status here > >>> > >>> when accessing /$/status I am not getting no results on a Fuseki - > >> version > >>> 3.8.0 instance with an enabled admin console > >>> > >>> curl -u admin:******* http://localhost:3030/$/status > >>> > >>> get's me a 404 while I can see the results and stats in the web admin. > >> > > > > > -- --- Marco Neumann KONA
