[Geoserver-users] WMTS Cascade

GeoServer GeoServer User
1

Hi,

When trying to connect to a WMTS service using the cascade option I can access the remote service if I put the authentication token into the URL but it doesn’t work if I use the HTTP header options. However if you put it into the URL it then doesn’t seem to be in the request URL’s when you try to actually access the layer via GeoServer.

I set my logging to GEOTOOLS and found the request URL’s but the authentication token is missing. Is that a bug or am I doing something wrong?

Cheers,

Paul

2

Hi,

What version are you on? It could certainly be a bug you spotted there.

By "I use the HTTP header options" do you mean the Username / password fields, or the "HTTP header name" / "HTTP header value"?

Regards,

Roar Brænden

4. feb. 2021 kl. 17:09 skrev Paul Wittle <paul.wittle@anonymised.com>:

Hi,

When trying to connect to a WMTS service using the cascade option I can access the remote service if I put the authentication token into the URL but it doesn’t work if I use the HTTP header options. However if you put it into the URL it then doesn’t seem to be in the request URL’s when you try to actually access the layer via GeoServer.

I set my logging to GEOTOOLS and found the request URL’s but the authentication token is missing. Is that a bug or am I doing something wrong?

Cheers,
Paul
This e-mail and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed. It may contain unclassified but sensitive or protectively marked material and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All traffic may be subject to recording and/or monitoring in accordance with relevant legislation. Any views expressed in this message are those of the individual sender, except where the sender specifies and with authority, states them to be the views of Dorset Council. Dorset Council does not accept service of documents by fax or other electronic means. Virus checking: Whilst all reasonable steps have been taken to ensure that this electronic communication and its attachments whether encoded, encrypted or otherwise supplied are free from computer viruses, Dorset Council accepts no liability in respect of any loss, cost, damage or expense suffered as a result of accessing this message or any of its attachments. For information on how Dorset Council processes your information, please see www.dorsetcouncil.gov.uk/416433 <http://www.dorsetcouncil.gov.uk/416433&gt; _______________________________________________
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: Earning Your Support Instead of Buying it
- The GeoServer user list posting guidelines: User group posting guidelines

If you want to request a feature or an improvement, also see this: Successfully requesting and integrating new features and improvements in GeoServer · geoserver/geoserver Wiki · GitHub

Geoserver-users@lists.sourceforge.net <mailto:Geoserver-users@anonymised.comeforge.net>
https://lists.sourceforge.net/lists/listinfo/geoserver-users

3

Hi,

Thanks for getting back to me but yes it was the “HTTP header name”/ “HTTP header value” options.

Thanks,

Paul

···

From: Roar Brænden <roar.brenden.no@…84…>
Sent: 04 February 2021 22:21
To: Paul Wittle <paul.wittle@…9945…>
Cc: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] WMTS Cascade

Hi,

What version are you on? It could certainly be a bug you spotted there.

By “I use the HTTP header options” do you mean the Username / password fields, or the “HTTP header name” / “HTTP header value”?

Regards,

Roar Brænden

  1. feb. 2021 kl. 17:09 skrev Paul Wittle <paul.wittle@…9945…>:

Hi,

When trying to connect to a WMTS service using the cascade option I can access the remote service if I put the authentication token into the URL but it doesn’t work if I use the HTTP header options. However if you put it into the URL it then doesn’t seem to be in the request URL’s when you try to actually access the layer via GeoServer.

I set my logging to GEOTOOLS and found the request URL’s but the authentication token is missing. Is that a bug or am I doing something wrong?

Cheers,

Paul

This e-mail and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed. It may contain unclassified but sensitive or protectively marked material and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All traffic may be subject to recording and/or monitoring in accordance with relevant legislation. Any views expressed in this message are those of the individual sender, except where the sender specifies and with authority, states them to be the views of Dorset Council. Dorset Council does not accept service of documents by fax or other electronic means. Virus checking: Whilst all reasonable steps have been taken to ensure that this electronic communication and its attachments whether encoded, encrypted or otherwise supplied are free from computer viruses, Dorset Council accepts no liability in respect of any loss, cost, damage or expense suffered as a result of accessing this message or any of its attachments. For information on how Dorset Council processes your information, please see www.dorsetcouncil.gov.uk/416433 _______________________________________________
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:

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

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users