Miles - Sadly, neither of those settings had any effect. I'm beginning to suspect this is something of a lost cause, at least in the 6.1,1 version I'm running.
Thanks, Adam On Mon, Sep 19, 2016 at 11:45 PM, Adam McCullough <amccullo...@imvu.com> wrote: > Miles -- I'll take a look at those settings and see if they change > anything. > > Reindl -- I absolutely see your point, but that's not really within the > scope of what I can attempt. I'm trying to stand up a replacement caching > proxy, not refactor the backing app. > > Not saying you're wrong, just that it's outside the scope of what I'm > trying to do (and capable of doing at the moment). > > Thanks, > > Adam > > On Mon, Sep 19, 2016 at 11:38 AM, Reindl Harald <h.rei...@thelounge.net> > wrote: > >> >> >> Am 19.09.2016 um 20:23 schrieb Miles Libbey: >> >>> A few more settings to look at: >>> proxy.config.cache.max_doc_size >>> proxy.config.http.max_post_size (if they are POSTs?) >>> >> >> that's all nice *but* a URL longer than 8K is a fractal of bad design of >> whatever applications doing that instead using POST for a million reasons >> and if it's only that you have the full data in your access logs >> >> we have a mod_security limit of 255 chars for a URL over many years now >> and every application which can't live with that is checked if it#s really >> needed - that fact would be a 99.999% chance to deny the "really" part when >> it's not fixable >> > >
