GeoServer

WCS capabilities do include invalid links (CITE failure)

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Blocker Blocker
  • Resolution: Fixed
  • Affects Version/s: 1.6.3
  • Fix Version/s: 1.6.4
  • Component/s: WCS
  • Labels:
    None
  • Number of attachments :
    0

Description

The capabilities now get out with stuff like:
http://localhost:8080/geoserver/wcs?/GetCapabilities?

OMG...

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Andrea Aime added a comment -

This is due to a couple of things:

  • the capabilities requests using the "ows/" path:
    http://localhost:8080/geoserver/ows?service=WCS&request=GetCapabilities
    instead of the old WCS path (btw, when did this happen and why?)
  • the code in the wcs capabilities using Request.isDispatchedRequest, which
    is doing some magic trick to handle a transition between servlets and the
    dispatcher. I checked, it's being used only by WCS capabilities, I guess it
    can be safely removed now? There are no WCS servlets registered anywhere.
Show
Andrea Aime added a comment - This is due to a couple of things:
  • the capabilities requests using the "ows/" path: http://localhost:8080/geoserver/ows?service=WCS&request=GetCapabilities instead of the old WCS path (btw, when did this happen and why?)
  • the code in the wcs capabilities using Request.isDispatchedRequest, which is doing some magic trick to handle a transition between servlets and the dispatcher. I checked, it's being used only by WCS capabilities, I guess it can be safely removed now? There are no WCS servlets registered anywhere.
Hide
Permalink
Andrea Aime added a comment -

Fixed on 1.6.x and trunk

Show
Andrea Aime added a comment - Fixed on 1.6.x and trunk

People

Vote (0)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.