solved update on large file upload issues

it wont allow even files 346 megs ..in ff and edge browsers
ff gives no real error that explains it edge gives this error
HTTP413: PAYLOAD TOO LARGE - The server is refusing to process a request because the request entity is larger than the server is willing or able to process.

ive put cloudflare in development mode bypassing it ive cleared all server edge server browser caches

i found an old cloudflare ticket on same issue that said it worked in chrome, but no other browsers



--
soaringeagle
head dreadhead at dreadlocks site
glider pilot student and member/volunteer coordinator with freedoms wings international soaring for people with disabilities
updated by @soaringeagle: 10/29/15 01:22:33PM

ok in chrome i get this error (expanded)
https://www.dreadlockssite.com/core/upload_file/?upload_name=video_file&fie…2Cmp4%2Cmpg%2Cogv%2Cwebm%2Cwmv&multiple=false&pm_video_file=dreadlocks.mp4 413 (Request Entity Too Large)qq.extend._upload @ S13fcd0af863a289ee8249a648d6eb924.js:56qq.UploadHandlerAbstract.upload @ S13fcd0af863a289ee8249a648d6eb924.js:44qq.FileUploaderBasic._uploadFile @ S13fcd0af863a289ee8249a648d6eb924.js:24qq.FileUploaderBasic._uploadFileList @ S13fcd0af863a289ee8249a648d6eb924.js:23qq.FileUploaderBasic._onInputChange @ S13fcd0af863a289ee8249a648d6eb924.js:21qq.UploadButton.onChange @ S13fcd0af863a289ee8249a648d6eb924.js:19(anonymous function) @ S13fcd0af863a289ee8249a648d6eb924.js:43


--
soaringeagle
head dreadhead at dreadlocks site
glider pilot student and member/volunteer coordinator with freedoms wings international soaring for people with disabilities

ah.

http://www.checkupdown.com/status/E413.html

think that last line is a hint: "....set by the Web server....."

Points to a server setting.

yes though every setting we tried hasnt gotten it


--
soaringeagle
head dreadhead at dreadlocks site
glider pilot student and member/volunteer coordinator with freedoms wings international soaring for people with disabilities

ok i have tried every fix there is on every forum

now heres what i just uncovered
413 Payload Too Large (RFC 7231)
The request is larger than the server is willing or able to process. Called "Request Entity Too Large " previously.

and
6.5.11. 413 Payload Too Large

The 413 (Payload Too Large) status code indicates that the server is
refusing to process a request because the request payload is larger
than the server is willing or able to process. The server MAY close
the connection to prevent the client from continuing the request.

If the condition is temporary, the server SHOULD generate a
Retry-After header field to indicate that it is temporary and after
what time the client MAY try again.


most recent attempts to fix it involved setting
LimitRequestBody
set to unlimited
SSLRenegBufferSize
set very high

upgraded php too
dded some odbc settings in my.cnf to limit cpu overuse
ive got it tuned to handled much more requests per second but cant solvde this large file upload limit
i have all cachings on all pages with create in the ur disabled
(varnish and coudflare)
i just dont know what else to try


--
soaringeagle
head dreadhead at dreadlocks site
glider pilot student and member/volunteer coordinator with freedoms wings international soaring for people with disabilities

seems most likely to be an issue with SSLRenegBufferSize
this has been a nightmare to figure out
this setting you might want to add to the htaccess increzasing it by default
i wont be sure its fixed till tomorow morning
but i think this is the issue since i tried every other ossible fix i can find


--
soaringeagle
head dreadhead at dreadlocks site
glider pilot student and member/volunteer coordinator with freedoms wings international soaring for people with disabilities

nothing server side has fixed it
when your able and have time i might need you to take a closer look at it


--
soaringeagle
head dreadhead at dreadlocks site
glider pilot student and member/volunteer coordinator with freedoms wings international soaring for people with disabilities
updated by @soaringeagle: 09/27/15 07:34:34AM

its fixed! 1 of the settings fixed it after rebooting server (restarting services didnt do it0)
but have to run 2-3 more tests to rule out some caching options


--
soaringeagle
head dreadhead at dreadlocks site
glider pilot student and member/volunteer coordinator with freedoms wings international soaring for people with disabilities

man i wanna curse and scream now
for 6 months cloudflare had lied to me
i demanded a full refund from the second i upgraded to pro


--
soaringeagle
head dreadhead at dreadlocks site
glider pilot student and member/volunteer coordinator with freedoms wings international soaring for people with disabilities

sorry, had no internet for the last 4ish days. Back home in a couple of days.

Glad to hear you got it sorted out.