implement url translation for legacy urls

[C0rby]

First draft of the URL translation for OC10 URLS.
This implements a redirect from the old OC10 URL format to the current format we use in oCIS web. Currently only the public link and the old files app URL work because we don't do any file lookups by id yet. If this needs to be supported we would need to figure out how to lookup file based on their OC10 id.

To test this you need to apply this diff to oCIS and add a replace for reva to the go.mod file:

diff --git a/proxy/pkg/proxy/proxy.go b/proxy/pkg/proxy/proxy.go
index b066e9631..1d73b08b5 100644
--- a/proxy/pkg/proxy/proxy.go
+++ b/proxy/pkg/proxy/proxy.go
@@ -328,6 +328,10 @@ func defaultPolicies() []config.Policy {
                                        Endpoint: "/index.php/",
                                        Backend:  "http://localhost:9140",
                                },
+                               {
+                                       Endpoint: "/apps/files/",
+                                       Backend:  "http://localhost:9140",
+                               },
                                {
                                        Endpoint: "/data",
                                        Backend:  "http://localhost:9140",

[update-docs]

Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes.

[lgtm-com]

This pull request introduces 1 alert when merging 3c1f98c into 756bdce - view on LGTM.com

new alerts:

• 1 for Open URL redirect

[lgtm-com]

This pull request introduces 1 alert when merging c9bbb4d into 011bc08 - view on LGTM.com

new alerts:

• 1 for Open URL redirect

[C0rby]

@labkode @butonic, this PR implements the OC10 URL redirect to oCIS.
Currently only index.php/s/<token> (public links) and apps/files/?dir=/Documents&fileid=32 are supported. But for the second URL only the dir parameter is used.

Is the lookup by fileid required? If so, how should we implement this? Do we need to access the OC10 database or is that information accessible somewhere in reva?

[lgtm-com]

This pull request introduces 1 alert when merging 8ac6d09 into 969ac3c - view on LGTM.com

new alerts:

• 1 for Open URL redirect

[lgtm-com]

This pull request introduces 1 alert when merging 73c8aee into 969ac3c - view on LGTM.com

new alerts:

• 1 for Open URL redirect

[C0rby]

To move forward with this I would propose to merge this PR in this state and if necessary implement the fileid based lookup later on.

This PR will allow the following:

• oc10.example.com/apps/files/?dir=/Photos&fileid=10 -> ocis.example.com/#/files/list/all/Photos
• oc10.example.com/s/TttylAos50jEApg -> ocis.example.com/#/files/public/list/TttylAos50jEApg

Also I think the lgtm bot alert can be ignored since this is not an open redirect.
The target URL is always fixed to the configured public URL.
So the user will either get redirected to:

• a login
• the requested path
• a not found page

[lgtm-com]

This pull request introduces 1 alert when merging a8f6ef8 into 969ac3c - view on LGTM.com

new alerts:

• 1 for Open URL redirect