[Web Client] Stop using hashbangs; use human-readable "pretty" URLs

Feature Suggestions
1

Current URL syntax:

https://my.plexapp.com/web/#!/server/f6d20f5a827fb55a91b4e6747bd19f81053b422c/details/%2Flibrary%2Fmetadata%2F11936

^ Ugly, and doesn't provide a lot of useful information to the average user

Suggested syntax:

https://my.plexapp.com/web/server/rcombs-NAS/series/Nichijou/season/1/episode/10

^ More concise, provides just as much information (though it requires a couple extra DB lookups when parsing), and looks much nicer.

Browsers without support for pushState/popState could fall back to inserting a hashbang after /web/, as is the current behavior.

2

I think one of the reasons the URLs are like that is that Plex does not yet do SSL by default thus ALL of your specific movie activity would be encrypted and easy to guess.

3

Moot point, as auth tokens/cookies are currently sent along with the URL.

4

Hey Rodger.. Now that you work at Plex you could just fix it yourself =P

I figure you already wanted to do this... but just forgot.

5

Moot point, as auth tokens/cookies are currently sent along with the URL.

Not a moot point, since the suggested url is easily guessable, where the current is not.  Sure they can both be harvested and reused, but only one of them is open to extrapolating more valid urls from a single capture or worse, a port/service scan.

That said, the current (in)security of PMS troubles me.