Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GeoServer metadata url links contain xml encoding #115

Closed
ingenieroariel opened this issue Jan 13, 2011 · 5 comments
Closed

GeoServer metadata url links contain xml encoding #115

ingenieroariel opened this issue Jan 13, 2011 · 5 comments
Milestone

Comments

@ingenieroariel
Copy link
Member

The online resource links in GeoServer's wms capabilities have a bunch of & in them, which make it so it's not a url that can be followed:

text/xml

Should be:

http://demo.geonode.org/geonetwork/srv/en/csw?outputschema=http://www.isotc211.org/2005/gmd&service=CSW&request=GetRecordById&version=2.0.2&elementsetname=full&id=7bbcae0b-37ba-46f1-8293-3bb5598d7964

Likely due to an extra set of xml encoding somewhere

@jj0hns0n
Copy link
Contributor

This was found to still be the case. While the URL seems to be 'stored' properly in GeoServer (see #127) when it is output in the GetCapabilities, it is encoded which makes it an invalid URL. This seems to be a problem that needs to be addressed on the geoserver side of things. @rmarianski do you think you could take a look?

@jj0hns0n
Copy link
Contributor

@ingenieroariel
Copy link
Member Author

Is this still happening? Seems like a serious issue, @jj0hns0n it would be great to write a test case that fails because of this. That way we will know for sure when it has been fixed in geoserver land.

@rmarianski
Copy link
Contributor

Is this that the '&' characters are being encoded as "&" ? That actually should be the case because '&' characters are illegal in xml attribute values:

http://www.w3.org/TR/REC-xml/#NT-AttValue

@ingenieroariel
Copy link
Member Author

After reading http://stackoverflow.com/questions/6519457/ampersand-problem-in-xml-when-creating-a-url-string I agree with rmarianski. Any user of that getcaps record should parse the string before offering users to click on it. Closing as invalid.

capooti added a commit to capooti/geonode that referenced this issue Apr 26, 2017
Query Error fix and Django Admin Update
EmereArco pushed a commit to EmereArco/geonode that referenced this issue Jan 30, 2018
* risks app: removed unused index view code, show all hazards

* risks app: removed unused index view code, show all hazards
risks app: data view tests
risks app: code cleanup

* risks app: sync client code

* risks app: hazard types fixture

* risks app: new client code

* risks app: geometry view

* risks app: map poc

* risks app: map view poc - zoom out control

* risks app: poc map view cleanup

*  - Simplified geometries and improved populateau mgmt command

* merge with main topic

* risks app: map view poc - zoom out fixed

* risks app: updated client

* risks app: updated client

* risks app: updated client

* risks app: context data for client

* risks app GeoNode#32 end context url with slash

* risks app: GeoNode#26 ordering features in geoserver

* risks app: return empty dict instead of none

* risk app: client update

* risks app: GeoNode#26 data ordering in app

* risks app: GeoNode#23 layer params in risk data view

* risks app: return correct dimension order, layers api

* risks app: corrected order of values for non-default dimension selection

* risks app: GeoNode#30 additional layers associated with risk analysis

* risks app: GeoNode#30 risk additional layers tests

* risks app: GeoNode#30 risk additional layers - list of layers in risk data view

* risks app GeoNode#29: integrated client code

* risks app GeoNode#29: client app config files

* risks app: GeoNode#33 return layerAttributes

* risks app: GeoNode#33 return layerAttributes tests

* risks app: GeoNode#31 style layer associated with risk analysis

* risks app: GeoNode#31 style layer associated with risk analysis

* risks app: GeoNode#31 correct sld attribute

* risks app: make additional layers optional

* risks app: missing import for metadata parser

* risks app: missing import for metadata parser

* risks app: missing import for metadata parser

* risks app: GeoNode#42 corrected status update

* risks app: do not use hardcoded fid in data import

* risks app: use celery for running metadata import

* merge

* merge

* risks app: GeoNode#38 unification of data structures in risk data view

* risks app: GeoNode#63 renamed geonode key to baseurl

* risks app: deploy mapstore translations

* risks app: removed unused stylesheet link

* risks app: data model for cost benefit app

* risks app: db migration for cb app

* risks app: additional data importer

* risks app: cost benefit app

* risks app: new url structure

* risks app: new url structure

* risks app: include geometry view into app-specific namespace

* risks app: config for js client

* risks app: corrected geometry urls

* merge migrations

* mapstore update

* risks app: GeoNode#30 pdf report url

* risks app: GeoNode#30 rendering pdf report

* risk app: GeoNode#30 pdf gen with cli command

* risk app: GeoNode#102 move layer to risk analysis

* risks app: base template

* risks app: GeoNode#103 remove upload temp file, do not copy layer_attribute in migration

* risks app: GeoNode#103 importmetadata update, minor fixes

* risks app: GeoNode#103 layer association in data views

* risks app: GeoNode#102 tests update

* risks app: updated travis conf to use pg9.5

* risks app: updated travis conf

* risks app: updated travis conf

* risks app: tests - run geoserver

* risks app: tests - run geoserver

* risks app: tests - run geoserver with 30 sec delay

* risks app: tests - notification to cezio

* risks app: cost benefit index

* risks app: unifi risks templates

* risk app: unified urls

* risk app: unified urls v2

* risks app: layer title

* risks app: additional data tables
travislbrundage pushed a commit to travislbrundage/geonode that referenced this issue Feb 9, 2018
Disable update metadata button until the page has been fully loaded t…
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants