Handle path after short link

[jknphy]

Description

Add route for handling path of this kind: <shorten-url><path> Some tools like libzypp needs support for this, for example, http://updates.suse.com returns error 404 for the / path but the /repodata/repomd.xml file is served correctly.

Example of use

Example of use: curl -vI http://127.0.0.1:5000/9og4/repodata/repomd.xml

[okurz]

looks like a good start. Please extend https://github.com/sqozz/schort/blob/master/tests/functional_tests.py for the new feature

[sqozz]

What other solutions did you consider? For me it feels like you're abusing a link shortening service for a shortcoming in a different piece of software (libzypp apparently needs such function to work properly?). Did you consider using a regular web server to rewrite your paths instead? E.g. in nginx you can do something like:

location = /short {
     return 301 https://a.very.long/path/to/some/subfolder/on/some/server
}

what is also missing:

• test(s)
• user facing explanation of this feature - e.g. in https://github.com/sqozz/schort/blob/master/templates/index.html#L22

[jreidinger]

Let me here explain rationale for this features:
on s390 ( mainframes ) there is a limitation how long line can be passed to kernel command line. On this command line we pass URL that leads to installation repository ( that for http has defined API structure ). We use this url shorter for testing purpose ( due to very easy creation of short url for some long testing repository ).
And here comes one shortcomming that we would like to address with this pull request. schort cannot handle subpath. Basically if we access something like http://127.0.0.1:5000/9og4it works, but if library for repository management tries to use http://127.0.0.1:5000/9og4/repodata/repomd.xml to read repository metadata schort returns 404 instead of redirection to given subpath.
So this short pull request allows in general to shorten root URL of API. And client lib can use shot URL to access even subpaths of that API ( thinking about something like REST API ).

nginx way with using directory way of location will probably work, but it miss the nice way of schort to generate short API on fly for testing versions of repository(API).

[sqozz]

I understand. My main problem with this is that schort currently does a 1 to 1 mapping, meaning 1 schort link points to 1 remote destination. This already caused problems in the past to me as my provider received abuse reports because these short links get (abused) to hide malicious content.
With this PR, you can hide even more behind a single short link (for you, this is a feature) and I fear this makes it even harder for public schort instances to exist.

Can you provide a full example of the long URL (you can replace secret stuff with random strings)? Is it really that dynamic that you need a tool with API access to create shorter paths?