url-encode http/https Path Substitution

[krog 0]

Hello,

 

I use emby together with kodi in a direct play configuration (iso playback is one reason). Path substritution is working fine with smb, nfs, sftp... because you can exactly replicate the way a manual kodi source would look. As I get better seek performance with http/https vs. smb and can connect to this kind of source from everywhere, I tried path substitution with a matching http path.

 

Problem: The part of the file location that is not substituted does not get encoded and the http server cannot find the file. A shortend example from my access.log:

 

Manual http(s) Source (working 200):

GET /amazon/Videos/Movies/My%20movie%20name%20(1234)/My%20movie%20name%20-%20%5b1080p24.BluRay.x264%5d.mkv HTTP/1.1 200

 

Emby Path Substitution (fails 404):

GET /amazon/Videos/Movies/My movie name (1234)/My movie name - [1080p24.BluRay.x264].mkv HTTP/1.1 404

 

 

A substitution starting with http/https:// needs to be url-encoded to work. As an alternative a switch to force url-encode would also work.

 

Bye Joerg

[Angelblue05 4130]

I really don't understand why you are doing this? You can play from HTTP/S instead of smb, using your server. Just enable the option in the addon settings > playback > play from HTTP

 

Otherwise, a pull request is welcome since your setup is outside the norms of what the addon does.

 

 

Sent from my iPhone using Tapatalk

[gstuartj 39]

(Deleted. Misinterpreted something.)

Edited October 28, 2016 by gstuartj

[Luke 37060]

He's using a neat trick to host copies of his files on Amazon. Yes we can get this figured out I would think.

[Angelblue05 4130]

Ok. And it just needs to be url encoded. I get that. But is the path to amazon in emby as a path substitution? Or was this in kodi?

 

 

Sent from my iPhone using Tapatalk