Filter parameter exceeded URL length

Hi,

We are using the static embed option to embed our report in our client access portal.

One of our reports requires a filter for long text (course title). When our client uses this filter, the course titles they select exceed the URL length.

We provide a library of courses, so it is necessary for our clients to be able to select the courses they want to report on freely.

We did some testing ourselves where we selected 56 courses by the title and the URL is 51K characters. It is terrible I know, but is there any way we can bypass this issue without having to change the filter?

Thanks
Jennifer

The URL length may be getting limited upstream of Metabase. Are you running Metabase through a reverse proxy, like nginx? There’s a discussion thread where someone is using IIS as a reverse proxy and it has very, very small default URL length limits. I’m not sure what modern browser limits are.

Do you have a unique ID number associated with these courses?

Just to post an update on this. Metabase support suggested I increase the header size, luckily we are self-hosting, so we can increase it on our end. However, our developers did point out that we will hit the browser or proxy limit anyway. So we would only increase it up to a certain point.

Did you fix it with the variable `MB_JETTY_REQUEST_HEADER_SIZE`?

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