#12 Encoded URLs are not treated properly

[Joerg Delker]

My UPnP client requests URLs like
http://192.168.1.100:49152/content/media/object_id%3D59%26res_id%3D0
rather than
http://192.168.1.100:49152/content/media/object_id=59&res_id=0

While both URLs are identical from the specification point of view, mediatomb only works with the latter.

The first produces a "404 not found".

[Jin]

Logged In: YES
user_id=1205152
Originator: NO

Hmm, actually we did take care of that, so if it does not work anymore then we probably break that functionality. Thanks for reporting the issue, I will look into it.

[Jin]

Logged In: YES
user_id=1205152
Originator: NO

OK.. please take a look at revision 1553.

I still need to check if this does not break the compatibility for one broken renderer, but I think it should be fine.

[Jin]

Logged In: YES
user_id=1205152
Originator: NO

fixed in rev 1553