[prev in list] [next in list] [prev in thread] [next in thread]
List: nginx
Subject: Re: I need help with our NGINX set up
From: zen zenitram <quickfire28 () gmail ! com>
Date: 2024-05-01 5:35:32
Message-ID: CAFNpnkdbaHmk4J5HFBQwzBVcJUhhqjKncHSx2n3TbU=UqKY=7w () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
We dont use PHP, our system use perl cgi.
So the problem is in cgi?
On Wed, May 1, 2024, 8:57 AM Dan Swaney <justdan23@gmail.com> wrote:
> The clue is with the URL which failed.
>
> From first look, you appear to be using a FAST CGI URL with PHP?
>
> Just a wild guess, but try using:
> ```
>
> fastcgi_param PHP_VALUE "upload_max_filesize = 500M \n post_max_size=500M"
>
> ```
>
> Here is a reference link mentioning it:
> https://serverfault.com/a/704209
>
> On Tue, Apr 23, 2024, 4:49 AM zen zenitram <quickfire28@gmail.com> wrote:
>
>> Good day!
>>
>> Here is what happen when we try to upload file more than 128 kb. Too
>> check if it is on server side we run the server without nginx and it can
>> upload larger size files.
>>
>> Thank you!
>>
>>
>>
>> On Fri, Apr 19, 2024 at 6:18 PM Reinis Rozitis via nginx <nginx@nginx.org>
>> wrote:
>>
>>> > It only accepts maximum of 128 kb of data, but the
>>> client_max_body_size 500M;. Is there a way to locate the cause of error.
>>>
>>> Can you actually show what the "error" looks like?
>>>
>>> The default value of client_max_body_size is 1M so the 128Kb limit most
>>> likely comes from the backend application or server which handles the POST
>>> request (as an example - PHP has its own post_max_size /
>>> upload_max_filesize settings).
>>>
>>>
>>>
>>> p.s. while it's unlikely (as you specify the settings in particular
>>> location blocks) since you use wildcard includes it is always good to check
>>> with 'nginx -T' how the final configuration looks like. Maybe the request
>>> isn't handled in server/location block where you expect it ..
>>>
>>> rr
>>> _______________________________________________
>>> nginx mailing list
>>> nginx@nginx.org
>>> https://mailman.nginx.org/mailman/listinfo/nginx
>>>
>> _______________________________________________
>> nginx mailing list
>> nginx@nginx.org
>> https://mailman.nginx.org/mailman/listinfo/nginx
>>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> https://mailman.nginx.org/mailman/listinfo/nginx
>
[Attachment #5 (text/html)]
<div dir="auto">We dont use PHP, our system use perl cgi.<div dir="auto">So the \
problem is in cgi?</div><div dir="auto"><br></div></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, May 1, 2024, 8:57 AM \
Dan Swaney <<a href="mailto:justdan23@gmail.com">justdan23@gmail.com</a>> \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">The clue is with \
the URL which failed. <div dir="auto"><br></div><div dir="auto">From first look, \
you appear to be using a FAST CGI URL with PHP?</div><div dir="auto"><br></div><div \
dir="auto">Just a wild guess, but try using:</div><div dir="auto">```</div><div \
dir="auto"><div style="margin:0px;padding:0px;border:0px;font-family:-apple-system,blinkmacsystemfont,"segoe \
ui adjusted","segoe ui","liberation \
sans",sans-serif;vertical-align:baseline;width:307.491px;color:rgb(12,13,14);background-color:rgb(255,255,255)" \
dir="auto"><pre style="margin-top:0px;margin-bottom:0px;border:0px;font-style:inherit; \
font-variant:inherit;font-weight:inherit;vertical-align:baseline;width:auto;max-height:600px"><code \
style="margin:0px;padding:0px;border:0px;font-style:inherit;font-variant:inherit;font- \
weight:inherit;line-height:inherit;vertical-align:baseline;background-color:transparent;white-space:inherit;border-radius:0px">fastcgi_param \
PHP_VALUE "upload_max_filesize = 500M \n \
post_max_size=500M"</code></pre></div></div><div dir="auto">```</div><div \
dir="auto"><br></div><div dir="auto">Here is a reference link mentioning \
it:</div><div dir="auto"><a href="https://serverfault.com/a/704209" target="_blank" \
rel="noreferrer">https://serverfault.com/a/704209</a></div></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Apr 23, 2024, 4:49 AM \
zen zenitram <<a href="mailto:quickfire28@gmail.com" target="_blank" \
rel="noreferrer">quickfire28@gmail.com</a>> wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr">Good day!<div><br></div><div>Here is what \
happen when we try to upload file more than 128 kb. Too check if it is on server side \
we run the server without nginx and it can upload larger size \
files.</div><div><br></div><div>Thank \
you!<br><div><div><br></div><div><br></div></div></div></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Apr 19, 2024 at \
6:18 PM Reinis Rozitis via nginx <<a href="mailto:nginx@nginx.org" \
rel="noreferrer noreferrer" target="_blank">nginx@nginx.org</a>> \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">> It only accepts \
maximum of 128 kb of data, but the client_max_body_size 500M;. Is there a way to \
locate the cause of error.<br> <br>
Can you actually show what the "error" looks like?<br>
<br>
The default value of client_max_body_size is 1M so the 128Kb limit most likely comes \
from the backend application or server which handles the POST request (as an \
example - PHP has its own post_max_size / upload_max_filesize settings).<br> <br>
<br>
<br>
p.s. while it's unlikely (as you specify the settings in particular location \
blocks) since you use wildcard includes it is always good to check with 'nginx \
-T' how the final configuration looks like. Maybe the request isn't handled \
in server/location block where you expect it ..<br> <br>
rr<br>
_______________________________________________<br>
nginx mailing list<br>
<a href="mailto:nginx@nginx.org" rel="noreferrer noreferrer" \
target="_blank">nginx@nginx.org</a><br> <a \
href="https://mailman.nginx.org/mailman/listinfo/nginx" rel="noreferrer noreferrer \
noreferrer" target="_blank">https://mailman.nginx.org/mailman/listinfo/nginx</a><br> \
</blockquote></div> _______________________________________________<br>
nginx mailing list<br>
<a href="mailto:nginx@nginx.org" rel="noreferrer noreferrer" \
target="_blank">nginx@nginx.org</a><br> <a \
href="https://mailman.nginx.org/mailman/listinfo/nginx" rel="noreferrer noreferrer \
noreferrer" target="_blank">https://mailman.nginx.org/mailman/listinfo/nginx</a><br> \
</blockquote></div> _______________________________________________<br>
nginx mailing list<br>
<a href="mailto:nginx@nginx.org" target="_blank" \
rel="noreferrer">nginx@nginx.org</a><br> <a \
href="https://mailman.nginx.org/mailman/listinfo/nginx" rel="noreferrer noreferrer" \
target="_blank">https://mailman.nginx.org/mailman/listinfo/nginx</a><br> \
</blockquote></div>
[Attachment #6 (text/plain)]
_______________________________________________
nginx mailing list
nginx@nginx.org
https://mailman.nginx.org/mailman/listinfo/nginx
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic