BaseURL Path Handling Bug about scs-key-client HOT 1 CLOSED

Upon investigation, there are four methods which need to be considered. The URI path component of three of these are constrained by the OpenPGP HTTP Keyserver Protocol (HKP). To make this bug more specific:

• (*Client).GetKey() - uses HKP via (*Client).PKSLookup(), see below.
• (*Client).GetVersion() - should be constructed by appending /version to any path component specified by (*Config).BaseURL. This is not consistent with the current behaviour.
• (*Client).PKSAdd() - the absolute path is set to /pks/add (ref). This is consistent with the current behaviour.
• (*Client).PKSLookup() - the absolute path is built up of the base request /pks/lookup, followed by any variables (ref). This is consistent with the current behaviour.

I also took a brief look at how the gpg command-line behaves when interacting with an HKP key server whose URI includes path component. This command:

gpg --keyserver pool.sks-keyservers.net/test --search-keys blah

Results in an HTTP GET request to /pks/lookup?op=index&options=mr&search=blah.

TLDR; this bug includes the behaviour of (*Client).GetVersion() only. The current behaviour of (*Client).GetKey(), (*Client).PKSAdd() and (*Client).PKSLookup() is correct and should not be modified.

from scs-key-client.