Hi David, whether this is a bug or not it's debatable, the OGC specs says that in a KVP request:
- keys are supposed to be case insensitive - values are supposed to be case sensitive So the Met Office extended the protocol in a way that's not compliant to the spec. That said, it's sometimes easier to make GeoServer more tolerant to odd behaviors of servers that are being cascaded, rather than fixing them. I'd suggest to report this to the Met office, and if that fails, open a request for improvement on GeoServer (as always, pull request more than welcomed, if you need directions just ask) Cheers Andrea On Sun, Mar 31, 2019 at 11:33 AM David Osborn <[email protected]> wrote: > Good Morning Group, > > > > I’m still very much a rookie with GeoServer and I’ve been trying to follow > the steps to cascade WMTS requests to the UK Met Office Datapoint service. > The service description is here: > > > > > https://www.metoffice.gov.uk/datapoint/support/documentation/inspire-layers-detailed-documentation > > > > I have hit a snag but I think that I know what the problem is. What I > don’t know is what I can do about it. > > > > If I put the GetCapabilities request into a browser (with the correct API > key, of course), I get a valid XML response. The form of the request is > like this: > > > > > http://datapoint.metoffice.gov.uk/public/data/inspire/view/wmts?REQUEST=getcapabilities&key=<API > key> > > > > When I paste that URL into Geoserver I get a “forbidden” error. Looking in > the linux command window where I launched the GeoServer, I see the error > and the URL that was sent to DataPoint. It is not the same as the one that > I pasted into the configuration page and the “key” parameter has been > capitalised - like this: > > > > > http://datapoint.metoffice.gov.uk/public/data/inspire/view/wmts?REQUEST=getcapabilities&KEY=<API > key> > > > > If I then copy that URL from the command window and paste it into the > browser, it fails with the same “forbidden” error. Changing “KEY” to “key” > cures the problem in the browser. > > > > So it looks like GeoServer is parsing the entered URL, reforming it and > sending it out to the remote server – except that it has capitalised a > parameter name, which breaks it. > > > > Can anyone offer any suggestions? Is this a candidate for a bug report? > > > > Many Thanks > > > > David > > > _______________________________________________ > Geoserver-users mailing list > > Please make sure you read the following two resources before posting to > this list: > - Earning your support instead of buying it, but Ian Turton: > http://www.ianturton.com/talks/foss4g.html#/ > - The GeoServer user list posting guidelines: > http://geoserver.org/comm/userlist-guidelines.html > > If you want to request a feature or an improvement, also see this: > https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer > > > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-users > -- Regards, Andrea Aime == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- *Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.*
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
