This repository has been archived by the owner on Apr 21, 2022. It is now read-only.
Getting error 414 (Request-URI Too Large) when trying to save serialised data as config value #112
Comments
|
Well, I got string compression working, but it's not pretty... // compress
btoa(pako.deflate(JSON.stringify(configToSave), { to: 'string' }))
...
// decompress
JSON.parse(pako.inflate(atob(configLoaded), { to: 'string'})Since I need to save config on each user interaction of certain types, doing so much work every time is truly cringe-worthy, so a proper solution would be much nicer. |
Closed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hey,
I'm building a Kepler.gl custom visualization (see here: https://github.com/team-blaze/custom_visualizations_v2/tree/kepler/src/examples/kepler) and it's almost there, except for an issue with trying to save its config.
Kepler has a bunch of customisations you can do in its own UI and an API to save the config to then later re-apply on top of the data. Which is very neat as it would be possible to have Looker send it data and then people can tweak how it looks which would then be persisted in the Look using the config.
However the serialised config seems to be too large to be saved as a URL query parameter so I'm getting a 414 (Request-URI Too Large) error.
Do you happen to have a POST endpoint to send this to as request body rather than the GET one using query parameters implemented by the library (ie
trigger("updateConfig", [xxx])? Or is there a workaround? The best one I could think of would be to decompose the object and serialise parts of it into different config parameters and then recompose it or maybe to compress the serialised string, but these aren't great.To get an idea about the size, here's the offending URL below (with some potentially sensitive info scrubbed):
The text was updated successfully, but these errors were encountered: