RCade: From the ticket I sent in I've had the following reply from Gog yesterday:
Hope this is of some help.
RCade
MarkoH01: So you've reported a bug in their client and they actually told you that there's a bug in the client? They should receive a trophy for their outstanding work as ... *cough* ... suppport. Completely unhelpful but it is quite funny at least.
Um, it wasn't clear until the confirmation that it's actually a bug in the client. Just because it manifests in Galaxy doesn't necessarily mean that Galaxy is the problem.
You can change something in a piece of software which is completely correct from a technical perspective, yet it uncovers an issue with a different system altogether. E.g. they could have made a change to the requests Galaxy sends out to the file servers and some kind of wrong configuration or outdated software on the server side was unable to handle the request. In that case it would still have been a change in the current version of the client that triggered the issue, but it wouldn't have been a bug in the client itself.
Just today I had a case at work, where functionality in an application was broken, but the issue was not caused by the application itself but by the IDP it relied on for said functionality.