I use a non caching Nginx proxy to map some path on port 80 to an application specific http server on another port.
That works quite well for almost all URLs, however long URLs containing Base64 encoded data are truncated early. They are truncated at very shot lengths, vastly before the large_client_header_buffers limit. For example, my application server recieve URLs like
/set/test_9_0/data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAEAAAABACAYAAACqaXHeAAAAtklEQVR4Xu3VwRHCMBTE0BgG
The original URL was running for about 1-2 kbytes. It seems that the original URL continued with %2B
in this example case right after the cut location. Why does Nginx cut the URL at this location, and how to prevent that? I still need the path translation, as the application will always serve some services at root path level.