the files concerned are hosted at https://SUBDOMAIN.sharefile.eu and have been made publically available.
The issue we are faced with happens when we try to access a publically shared file (no authentication needed) via its share id using the .NET SDK (which internally queries the REST API) exploited by our software product.
The share's base URI is persisted in code like this:
This base URI is combined using the share id to the following query:
However, this query returns nothing, but an error message: "Share: This link could not be found in the system." These kind of queries worked for years, but stopped working by February 15, 2019.
The shared item does exist and is unchanged for a couple of months.
Now, if we change the base URI accordingly to https://SUBDOMAIN.sf-api.eu/sf/v3/ and the query, respectively, to
the query works and returns the expected item. Note the change in the domain!
We learned recently that it is recommended to match the REST API domain with the share domain, so https://SUBDOMAIN.sharefile.eu with https://SUBDOMAIN.sf-api.eu. But nevertheless, the issue did not occur until February 15, 2019, working for years.The question is, what has been changed that make queries like this to suddenly fail? Is there a chance to recover the previous behavior? While we could change the code of future software releases, older software versions would render useless as we are talking about a crucial feature. So, this is not an acceptable solution.
We actually require that the previous behavior is restored, maybe temporarily, until we have considered other ways to keep our software product working.