Bug: Webhook URLs are capped at 512 characters

Plex Labs
1

I have a webhook I’m trying to set up that includes a token in the URL querystring - said token is very long, around 800 characters, and PLEX quietly truncates any URL you put into the webhook input to 512 characters on save, which is putting quite a damper on things. A larger limit would be nice - a few thousand would give me some space - every major browser allows at least 2048 characters, usually more.

This is a dupe of Webhook cuts off long urls ( 1000+ characters does not work), but that’s locked and closed with no action. I’d hope it’s not too hard to bump the number for those of us making homebrew automation APIs?

2

I suspect the limitation is database in the cloud, which is probably not going to change. Why would you need such a long URL? In most cases you can replace it with some sort of token which is used to look up the additional information.

3

It’s way, way easier to keep everything stateless inside the URL. I imagine the service whose token I’m consuming and passing along has the same philosophy, which is why it’s so long - it probably contains encrypted authentication data. I could make do with being able to send along a custom field with the body; but allowing more data in the URL querystring just seems easier?

4

Specifically, for context, an auth token/code for anilist is around 1000 characters long right now (thanks JSON Web Tokens!). I don’t really want to spin up a service whose only job is fetching auth tokens from shorter IDs for a hobby project for me and a few friends if I can help it, since then I need to worry about authentication myself, since I’m actually storing state (except I need to ensure mine fits within the 512 character limit)… Once I start applying that much effort I’m most of the way to rebuilding simkl :woman_shrugging:.

5

For you, yes. For us we’d need to alter a database schema and do a migration, which can be painful.

6

Just as a point of comparison, Github allows webhook URLs of length 1024 at least, which’d be just enough for me to squeeze in an auth token of this size into the URL.

PLEX’s own webapp makes many URLs where query parameters bring the length of the URLs to 500+ characters - and that has the benefit of the auth getting stored in a cookie. It really is a fairly small limit.

7

Hehe, I was also making an anilist hobby project in the locked thread, an anilist plex scrobbler. I remember having to swap to tautulli because plex webhooks became unreliable, and eventually switched to another media server.

But here was my last working code in dotnet core:

8

I’ll raise an internal issue.

9

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.