[users@httpd] Debian Apache 2.4 doesn't read configuration files

2020-10-29 Thread syscon edm
The apache 2.4 doesn't read configuration files. In apache2.conf I have: # Include the virtual host configurations: IncludeOptional sites-enabled/*.conf So it should read read every *config file in sites-enabled/ In that directory I have: ll sites-enabled/ total 4 lrwxrwxrwx 1 root root 35 Oct

Re: [users@httpd] Apache 2.4 can not access server sub-directory

2020-10-29 Thread syscon edm
Thanks Mark for quick response, I'm using: Distributor ID: Debian Description: Debian GNU/Linux 10 (buster) Release: 10 My web-page is working perfectly on Apache 2.2 (gentoo) I tried it Debian 2.4 on a new box and I have this problem. I don't know what else to try. On Thu, Oct 29, 2020 at 4:50

Re: [users@httpd] Apache 2.4 can not access server sub-directory

2020-10-29 Thread Mark Brodis
Are you perhaps using httpd on Linux and if so is it a Linux version with selinux? If that's your scenario, take a look at this, with selinux the file permissions are only half the story, you have to categorize data in other directories by setting the type. I just had to do this, was a bit of a l

[users@httpd] Apache 2.4 can not access server sub-directory

2020-10-29 Thread syscon edm
After installing apache 2.4 I can not access server subdirectory: server/admin/index.html Forbiden You don't have permission to access /admin/index.html on this server I can access index.html in a directory below /admin (server/index.html) but not the server/admin/index.html I even change the pe

Re: [users@httpd] Bad Gateway with large file upload [EXT]

2020-10-29 Thread eric tse
Thank you very much James :) On Thu, Oct 29, 2020 at 12:30 PM James Smith wrote: > Not sure about tuning the network – that is out of my skill set – I am > lucky at work to have a 1G connection to my desk so these sort of uploads > are not an issue. From home I only have around 18M so it is noti

RE: [users@httpd] Bad Gateway with large file upload [EXT]

2020-10-29 Thread James Smith
Not sure about tuning the network – that is out of my skill set – I am lucky at work to have a 1G connection to my desk so these sort of uploads are not an issue. From home I only have around 18M so it is noticeable how long uploads take. You may want to look to see if you have intermediate host

Re: [users@httpd] Bad Gateway with large file upload [EXT]

2020-10-29 Thread eric tse
Good afternoon James Thank you very much for your help. We are inside a working organization network. The client is using VPN. I don't know if you guys have a little bit more extra tips/directions to tune the enterprise network, if not, it is all okay for now. Thank you very much for your help.

RE: [users@httpd] Bad Gateway with large file upload [EXT]

2020-10-29 Thread James Smith
Is your test over a local network or over the internet. If the latter there is little you can do. HTTP upload was never really designed for large files like this. That’s why more languages/frameworks put a limit on the size of uploads. And these are usually in the 5-10M size. There are much be

Re: [users@httpd] Bad Gateway with large file upload

2020-10-29 Thread eric tse
Hi community, Thank you for your valuable hint again. Can we tune something from chrome? that can make chrome 147MB test works? Or we need to tune our network infrastructure? For now, I haven't been able to google anything yet. Thanks and regards, Eric On Thu, Oct 29, 2020 at 11:10 AM eric

Re: [users@httpd] Bad Gateway with large file upload

2020-10-29 Thread eric tse
Good morning, Thanks for your excellent tip last night. We have some significant turn around from an investigation perspective. We’ve done some additional testing this morning and had a surprising result. Does this provide any hints to the cause? Firefox 60 MB: bad gateway F

Re: [users@httpd] Bad Gateway with large file upload

2020-10-29 Thread @lbutlr
On 28 Oct 2020, at 18:05, eric tse wrote: > We’re are getting a Bad Gateway error returned when trying to upload large > files through an IE browser to our webserver. Have you tried with a currently supported browser? IE is on death watch. -- If I were you boys, I wouldn't talk or even thin