Re: [Geoserver-devel] Strange behavior with the GeoServer REST

Hi all, wanted to throw my two cents in about the IndexController. The IndexController currently builds the list of links from a private method inside of the IndexController, which makes it impossible to extend, override, or append to. Any logic or code that produces dynamic content should

Re: [Geoserver-devel] Strange behavior with the GeoServer REST

I agree it shouldn't be a release blocker. Since GeoServer and GWC have different rest entrypoints (/rest vs /gwc/rest), it might be an idea to have different sections for them in the index page. At the very least, a little thought should be put into presentation. Torben On Thu, Sep 28, 2017 at

Re: [Geoserver-devel] Strange behavior with the GeoServer REST

+1 (and thanks all for the feedback) On 09/29/2017 07:15 AM, Andrea Aime wrote: On Fri, Sep 29, 2017 at 12:25 AM, Torben Barsballe > wrote: Found the issue. Definately a bug in IndexController - it just blindly trims off the

Re: [Geoserver-devel] Strange behavior with the GeoServer REST

On Fri, Sep 29, 2017 at 12:25 AM, Torben Barsballe < tbarsba...@boundlessgeo.com> wrote: > Found the issue. Definately a bug in IndexController - it just blindly > trims off the first four characters (normally "rest") of the path when > constructing the index. > I don't think the original rest

[Geoserver-devel] Strange behavior with the GeoServer REST

Hi all, something doesn't look right with GeoServer REST. First the GWC end-points seem to be indexed and prefixed with EST ? Not sure what EST stands for: * est * est/diskquota * est/layers * est/masstruncate * est/seed.json * est/statistics Then when accessing the other REST

Re: [Geoserver-devel] Strange behavior with the GeoServer REST

I suppose it depends on whether we want to consider the GWC REST API a subset of the GeoServer REST API, or a separate API within the application. Given it's /gwc/rest rather than /rest/gwc it seems to make more sense to keep them separate. On 2017-09-28 03:25 PM, Torben Barsballe wrote: > Found

Re: [Geoserver-devel] Strange behavior with the GeoServer REST

I've got a simple fix for the GeoWebCache issue here: https://github.com/geoserver/geoserver/pull/2547 In the interests of a prompt release, I've just excluded the geowebcache endpoints (which is the same way the old index page worked). And I've made a bug report for it here:

Re: [Geoserver-devel] Strange behavior with the GeoServer REST

Found the issue. Definately a bug in IndexController - it just blindly trims off the first four characters (normally "rest") of the path when constructing the index. I don't think the original rest index included the gwc endpoints - is this something we want to have included? Torben On Thu, Sep

Re: [Geoserver-devel] Strange behavior with the GeoServer REST

Hi Nuno, I can confirm at least for the GWC endpoints that there are issues. I'm currently working on Swagger docs for those endpoints and they should look like: ~/geoserver/ - gwc/rest - gwc/rest/diskquota - gwc/rest/layers - gwc/rest/masstruncate - gwc/rest/seed.json -