Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Apache LimitRequestBody 0 #2043

Closed
wants to merge 2 commits into from
Closed

Apache LimitRequestBody 0 #2043

wants to merge 2 commits into from

Conversation

thechubbypanda
Copy link

@thechubbypanda thechubbypanda commented Jul 31, 2023

Removes the 1GB upload restriction, allowing the PHP setting to work again.

Thanks to @t-schuster for the patch suggestion

Fixes #1796

Signed-off-by: Keval Kapdee <keval@thechubbypanda.net>
@thechubbypanda thechubbypanda changed the title Apache LimitRequestBody 0 for #1796 Apache LimitRequestBody 0 Jul 31, 2023
@Etienne-Schmitt
Copy link

Can a maintaner validate this?
This is a real problem and having to mount a special config for apache or edit the .htaccess everytime work BUT is not as practical than this fix

@J0WI
Copy link
Contributor

J0WI commented Aug 10, 2023

Unfortunately it's not as simple as that. You can read more about it here: https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/big_file_upload_configuration.html

@t-schuster
Copy link

I still apply the same patch in my deployment, it is actually as simple as that.

@thechubbypanda
Copy link
Author

thechubbypanda commented Aug 11, 2023

We've all read the docs and come to the conclusion that this patch is literally the one thing stopping the PHP env variables from working fully. It is actually something that used to work until apache changed the default value for it.
Regardless, it is merely allowing for one less hurdle to jump through when trying to enable big file uploads.
I'd also point out that the docs are terrible. It took me 5 days to figure out what was going on and find this fix.
(I'm also aware I've messed up the brackets, will fix soon)

Signed-off-by: Keval Kapdee <keval@thechubbypanda.net>
@Etienne-Schmitt
Copy link

Can confirm this, I'm using this only fix on my container and just this fixed the problem.

Like mention earlier in older version of apache2 the default value for LimitRequestBody was 0 before now it's set as 1GiB, as you can see here:
https://httpd.apache.org/docs/2.4/mod/core.html#limitrequestbody

Maybe for some people there will be more problems, like badly configured reverse proxy or else, but on the images library/nextcloud:*-apache "flavor" it will fix this upload problem.

@Etienne-Schmitt
Copy link

Etienne-Schmitt commented Aug 14, 2023

It even was discussed on the AOI images maintain by nextcloud:
nextcloud/documentation#10989

So, can we have progress on this?

Edit: the issue #1796 was even brough up on nextcloud/documentation#10989, and NEXTCLOUD/DOCUMENTATION say than MAYBE this should be merged or adapt into another form (directly edit the apache main apache2.conf? idk...)

Regards,
(Sorry for the caps, it's simple but it's driving me nuts...)

@J0WI
Copy link
Contributor

J0WI commented Sep 14, 2023

I think I would prefer the implementation in #2065. That's a better compromise than setting it to unlimited for everyone.

@thechubbypanda
Copy link
Author

Closing in favour of #2065

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Apache images built after ~mid June 2022 introduce 1GB upload limit
4 participants