#1559 closed enhancement (wontfix)

ways to expose the value of client_max_body_size

Reported by: adrianovaroli@… Owned by:
Priority: minor Milestone:
Component: other Version: 1.6.x
Keywords: Cc:
uname -a: Linux jessie 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2+deb8u3 (2016-07-02) x86_64 GNU/Linux
nginx -V: nginx version: nginx/1.6.2 TLS SNI support enabled configure arguments: --with-cc-opt='-g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2' --with-ld-opt=-Wl,-z,relro --prefix=/usr/share/nginx --conf-path=/etc/nginx/nginx.conf --http-log-path=/var/log/nginx/access.log --error-log-path=/var/log/nginx/error.log --lock-path=/var/lock/nginx.lock --pid-path=/run/nginx.pid --http-client-body-temp-path=/var/lib/nginx/body --http-fastcgi-temp-path=/var/lib/nginx/fastcgi --http-proxy-temp-path=/var/lib/nginx/proxy --http-scgi-temp-path=/var/lib/nginx/scgi --http-uwsgi-temp-path=/var/lib/nginx/uwsgi --with-debug --with-pcre-jit --with-ipv6 --with-http_ssl_module --with-http_stub_status_module --with-http_realip_module --with-http_auth_request_module --with-http_addition_module --with-http_dav_module --with-http_geoip_module --with-http_gzip_static_module --with-http_image_filter_module --with-http_spdy_module --with-http_sub_module --with-http_xslt_module --with-mail --with-mail_ssl_module --add-module=/build/nginx-ryOGNl/nginx-1.6.2/debian/modules/nginx-auth-pam --add-module=/build/nginx-ryOGNl/nginx-1.6.2/debian/modules/nginx-dav-ext-module --add-module=/build/nginx-ryOGNl/nginx-1.6.2/debian/modules/nginx-echo --add-module=/build/nginx-ryOGNl/nginx-1.6.2/debian/modules/nginx-upstream-fair --add-module=/build/nginx-ryOGNl/nginx-1.6.2/debian/modules/ngx_http_substitutions_filter_module

Description

Is there a way to read the value of client_max_body_size from an app? That would eventually let me warn users that their upload would fail before submitting, like so:

  • server app reads the value from nginx
  • server app writes the value to a client-side js method that handles uploads
  • user tries to upload a file > client_max_body_size
  • js reads saved value, compares against file size, stops the upload and warns

Change History (1)

comment:1 Changed 18 months ago by mdounin

  • Resolution set to wontfix
  • Status changed from new to closed

I don't think trying to implement an interface to expose the value of client_max_body_size for a particular URI worth the effort. Especially given that there is already an interface to report that maximum body size is reached, and nginx uses it - error 413. Unfortunately, browsers fail to handle it properly.

If you want to warn users from javascript, consider writing appropriate limit in the javascript code or its configuration.

Note: See TracTickets for help on using tickets.