multipart servlet request; nested exception is java.lang.IllegalStateException: org.apache.tomcat.util.http.fileupload.FileUploadBaseits size (4719402) exceeds the configured maximum (1048576)] with root cause
org.apache.tomcat.util.http.fileupload.FileUploadBasebecause its size (4
我有一个lambda函数,它与Serverless框架一起部署,这给出了下面的错误,只有当有效负载太大时才会出现。但是看起来,如果负载太大,lambda就不会到达我的代码,如果是这样的话,AWS会返回一个没有头的响应。控制台
Access to XMLHttpRequest at 'https://my-lambda-endpoint' from origin 'http://localhost:30
://my.server.com/anything' When method post
Then status 413此测试失败并出现javax.net.ssl.SSLException: Broken pipe (Write failed)异常,因为服务器读取Content-Length标头并在读取有效负载之前立即拒绝请求/以413响应。我通过cURL验证了服务器行
Google HTTP/HTTPS云负载均衡器(也就是HTTP/HTTPS转发规则)上的URL的长度限制是多少?我收到了负载均衡器对HTTP/1.1413 Request Entity Too Large错误响应的报告:有办法调整长度限制吗?是否有方法(从负载均衡器度量或日志中)判断有多少请求由于长度限制而被拒绝?在StackDriver日志中似乎没有结果:相关问题:亚马逊AWS ELB长度