Moviein can't handle https

Bugs
1

I don’t know if this is a bug so much as a feature request, but since the web DAT does it just fine, I assume that there the libraries already exist in Touch.

2

Additionally, question marks are not allowed in URLS passed in movieins… this makes it hard to pass variables to a PHP script. I found a workaround that involves reading the URL in the PHP script, but in general, this could probably be considered a bug in Touch.

3

Additionally, question marks are not allowed in URLS passed in movieins

Anything else broken with URL support?

This is a real pain. Hope it can be fixed in the next release.

4

I have no experiment with such link, but did you try to put the question marks between apostrophe: ‘?’

5

I’ve added https support to the next 088 release.
Handling ? takes a bit more thinking because right now unicode characters that we don’t support get turned into ? by default, so that will need to be reconciled.
Thanks for pointing this out

6

Not having full URL spec compliance has meant a complex work-around for one of our projects (requesting the URL in python, caching locally and passing a rewritten file URL back to Touch).

Here’s an example of the kind of URLs we’d like to parse

tgtwn.s3.amazonaws.com/items/4f … WDEFA7A6AA

Would really appreciate full URL compliance before any IRI support. This should simply be percent-encoding any non-ASCII bytes.

URL spec
tools.ietf.org/html/rfc3986

IRI spec
tools.ietf.org/html/rfc3987

7

Hi. We’ve just fixed up our URL handling to more intelligently download files based on mime types.
I tried your example but it returns an XML output with the following.

AccessDenied Request has expired 50290B49C042570A 2012-11-14T09:07:11Z gLJ5QKALzJA+Ve1lslp9AnsAVPpffHNDX+u3GMTInhg40OC6STnCSin8IWkTKlAZ 2013-10-17T01:29:36Z

Do you have a more up to date example we can test our fix with?
You can email support@derivative.ca too if privacy is a concern.

Cheers
Rob.