Document Media upload failedDocument Media upload failedhttps://liferay.dev/en/c/message_boards/find_thread?p_l_id=119785333&threadId=1116554272024-03-29T02:35:00Z2024-03-29T02:35:00ZRE: Document Media upload failedChristoph Rabelhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1116717182018-11-26T14:21:44Z2018-11-26T14:21:44Z<p>I am not sure about your questions, I just had the problem before
with large headers. The problem is that you have to configure all
services the users with those big headers use. And all proxies and
loadbalancers in between. e.g. one of my customers has a loadbalancer
that looks into the first 4K of the header. If the header is larger,
it sometimes(!) discards the request. It was a lot of fun to find out,
why requests sometimes simply "vanished".</p>
<p> </p>
<p>1) I don't think so. Of course, your apache will need more memory per
request. It wouldn't be a big deal for my proxies because they have
enough spare ram. But if you have low end hardware and lots of
requests ...</p>
<p> </p>
<p>2) I have never measured that and I don't know of any benchmarks
covering that setting. It shouldn't be a big performance factor (IMO).
You mostly need more memory per request (8K -> 64K)</p>
<p> </p>
<p>3) No idea.</p>Christoph Rabel2018-11-26T14:21:44ZRE: Document Media upload failedJoey Wonghttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1116653932018-11-26T02:34:12Z2018-11-26T02:34:12Z<p>Yes, you can be absolutely correct.</p>
<p>I'll look into this.</p>
<p> </p>
<p>1. Will this setting open up the service to DDos or any security
attack vector?</p>
<p>2.Is the entirely going to cause a performance degration between
apache + Tomcat?</p>
<p>3. Any discussion on this in forum or slack?</p>
<p> </p>
<p>Thanks for the advice.</p>Joey Wong2018-11-26T02:34:12ZRE: Document Media upload failedChristoph Rabelhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1116643682018-11-25T20:03:55Z2018-11-25T20:03:55Z<blockquote>
<div class="quote-title">Christoph Rabel:</div>
<div class="quote">
<div class="quote-content">
<p>... IMHO this causes huge problems in the network ...</p></div></div></blockquote>
<p>Sorry, I was very unclear here!</p>
<p>I didn't mean that this setting causes problems, but having huge http
headers does. If you need that setting, it means that you probably
have very large http headers. If that's the case, you I'd recommend to
look into it and check if you could reduce their size!</p>Christoph Rabel2018-11-25T20:03:55ZRE: Document Media upload failedJoey Wonghttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1116637062018-11-25T18:25:00Z2018-11-25T18:25:00Z<blockquote>
<div class="quote-title">Christoph Rabel:</div>
<div class="quote">
<div class="quote-content">
<p>Are you sure you need to fiddle with
"ProxyIOBufferSize"? You only need this if you have
very large http-headers (e.g. people with lots of cookies). IMHO
this causes huge problems in the network, because every server,
loadbalancers and proxies, need to be configured to handle that.</p>
<p> </p>
<p>Note: Setting a connectionTimeout for ajp is a good idea since
the default time is unlimited. Had some problems with that
before. 600 is a bit short IMHO, but that depends on your usage,
large file downloads/uploads can easily take longer when clients
are in the internet ...</p></div></div></blockquote>
Not sure. One is for certain, setting this in httpd.conf and not
reflecting that in server.xml will cause this issue. Therefore, who ever
faces such can either remove the entry in httpd.conf or add into server.xml.<br />
<br />
Joey Wong2018-11-25T18:25:00ZRE: Document Media upload failedChristoph Rabelhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1116630242018-11-25T16:26:58Z2018-11-25T16:26:58Z<p>Are you sure you need to fiddle with "ProxyIOBufferSize"?
You only need this if you have very large http-headers (e.g. people
with lots of cookies). IMHO this causes huge problems in the network,
because every server, loadbalancers and proxies, need to be configured
to handle that.</p>
<p> </p>
<p>Note: Setting a connectionTimeout for ajp is a good idea since the
default time is unlimited. Had some problems with that before. 600 is
a bit short IMHO, but that depends on your usage, large file
downloads/uploads can easily take longer when clients are in the
internet ...</p>Christoph Rabel2018-11-25T16:26:58ZRE: Document Media upload failedOlaf Kockhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1116624092018-11-25T16:05:00Z2018-11-25T16:05:00Z<blockquote>
<div class="quote-title">Joey Wong:</div>
<div class="quote">
<div class="quote-content">
<p>Update: Found the problem. Is directly related to AJP
configuration in tomcat (server.xml) mismatch with Apache2 (Httpd.conf).</p></div></div></blockquote>
Thanks for the update. That cause/solution would have been close to
impossible to figure out here...Olaf Kock2018-11-25T16:05:00ZRE: Document Media upload failedJoey Wonghttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1116592892018-11-24T17:47:32Z2018-11-24T17:47:32Z<p>Update: Found the problem. Is directly related to AJP configuration
in tomcat (server.xml) mismatch with Apache2 (Httpd.conf).</p>
<p>In the httpd.conf a junior team member added; </p>
<p> </p>
<p>"ProxyTimeout 600<br /> ProxyIOBufferSize 65536"</p>
<p> </p>
<p>but didn't reflect the changes in server.xml ---- >
"<Connector port="8009" protocol="AJP/1.3" redirectPort="8443"/>"</p>
<p>It should be --> "<Connector port="8009"
protocol="AJP/1.3" <strong>packetSize="65536"</strong>
<strong>connectionTimeout="600"</strong> redirectPort="8443"/>"</p>
<p> </p>
<p>or ensure httpd.conf been commented off.</p>
<p> </p>
<p>Changes made requires service restart.</p>
<p> </p>Joey Wong2018-11-24T17:47:32ZDocument Media upload failedJoey Wonghttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1116554262018-11-23T17:58:23Z2018-11-23T17:58:23Z