Re: Set maxHttpHeaderSize in tomcat server as a parameter

Lingesh Mouleeshwaran

Hello All, 

Lingesh M

On Tue, Sep 18, 2018 at 8:06 AM, Daniel Mikusa <dmikusa@...> wrote:
On Mon, Sep 17, 2018 at 4:55 PM, <sajjadgholami2006@...> wrote:
I see what you mean Dan, I know that it doesn't need the whole repo to be forked and it's just tomcat configuration; but that still needs another 'public' repo to host the tomcat customized configuration.

It doesn't have to be public. It can be on a company's internal network. It just needs to be accessible from the platform where the buildpack is running. That's why it's convenient to use the Staticfile buildpack and host the config on the platform itself.
Look at it from a corporation's view, they don't want to trust more repositories than the formal open source repos having a support of a community and it's secure since the community has it under control, instead of my own public repo that I can mess it up anytime.

I wouldn't expect anyone to trust a random repo from the internet. They'd want to host their own Tomcat config on a server they control, like an app they push to their platform using the Staticfile buildpack.

Anyway, I probably do not fully understand your use case and that's OK. I just wanted to suggest this other option in case it might work for you.


That's my whole point, it can be a parameter exposed in the formal code base which everyone has trust on. 

Join to automatically receive all group messages.