RE: [users@httpd] Apache httpd directory listing no longer working

>> Alias /mydirectory / "/my/actual/location" >mismatch trailing slash a potential red flag her. The actual rule has a trailing slash (typo during obfuscation of real location) Alias /mydirectory / "/my/actual/location/" > what URL fails and what's the verbatin error_log entry? *

[users@httpd] Apache httpd dynamically links to wrong ssl library on macOS causing a crash

Hi, I’m currently working on a new php formula in the Homebrew package manager project where we have noticed that httpd crashes on macOS High Sierra under certain conditions. My question now is if this is a bug in Apache httpd that I should file in the bug tracker or if you can point me in the

Re: [users@httpd] E-commerce Rewrite Rule

Be wary of such blanket answers. When used in the per directory context (Directory block or .htaccess file), the leading slash is stripped before the rewrite rule is evaluated. Consider using the rewrite log to see what is happening. On Wed, Feb 14, 2018 at 4:38 AM,

[users@httpd] Apache httpd directory listing no longer working

Directory listing inside one of our VirtualHost configurations has stopped working recently. It now returns a 403 Forbidden when trying to access a directory. The url is protected with basic authentication from a .htpasswd file. Accessing a specific file under de location presents no problem. =>

RE: [users@httpd] E-commerce Rewrite Rule

The regex groups count from left to right, Also the paths start with a / So the rule should be something like: RewriteRule ^/([A-Za-z0-9-]+)/([A-Za-z0-9-]+)/([A-Za-z0-9-]+)/([A-Za-z0-9-]+)/?$ php-page-name.php?dept=$1=$2=$3=$4 [L] - Van: Rajib Karmakar

Re: [users@httpd] E-commerce Rewrite Rule

Hello, I build is it right? 3. domain.com / Clothing[Department] / Mens[Main Catagory] / Shirts[Sub Catagory] / White Shirt [product_id=15] => RewriteRule ^([A-Za-z0-9-]+)/([A-Za-z0-9-]+)/([A-Za-z0-9-]+)/([A-Za-z0-9-]+)/?$ php-page-name.php?dept=$4=$3=$2=$1 [L] 4. domain.com / contact-us =>

Re: [users@httpd] Apache httpd directory listing no longer working

On Wed, Feb 14, 2018 at 3:05 AM, wrote: > Directory listing inside one of our VirtualHost configurations has stopped > working recently. > It now returns a 403 Forbidden when trying to access a directory. > > The url is protected with basic authentication from a

[users@httpd] httpd running with uid - apache 2.4.29

All, I am experimenting a scratch install of Apache 2.4 on RHEL. I noticed the httpd process is running with UID instead of username. Any ideas? root 30426 1 0 14:40 ?00:00:00 /app/apache/apache24/bin/httpd -k start 3013930427 30426 0 14:40 ?00:00:00

Re: [users@httpd] httpd running with uid - apache 2.4.29

An idea : check that the username is not longer than 8 characters. 2018-02-14 21:45 GMT+01:00 renee ko : > All, > > I am experimenting a scratch install of Apache 2.4 on RHEL. I noticed the > httpd process is running with UID instead of username. Any ideas? > > root

Re: [users@httpd] httpd running with uid - apache 2.4.29

Hi, If the length of the username (If longer than 8 characters, then ps aux will substitute the uid for the name). On Wed, Feb 14, 2018 at 2:45 PM, renee ko wrote: > All, > > I am experimenting a scratch install of Apache 2.4 on RHEL. I noticed the > httpd process is

Re: [users@httpd] httpd running with uid - apache 2.4.29

changed to shorter username and it worked. thank you both. On Wed, Feb 14, 2018 at 2:58 PM, David Wright - NOAA Affiliate < david.e.wri...@noaa.gov> wrote: > Hi, > If the length of the username (If longer than 8 characters, then ps aux will > substitute the uid for the name). > > On Wed, Feb

Re: [users@httpd] E-commerce Rewrite Rule

You seem to be making the "urls" that the client gets unnecessarily complex which results in rewrite rules that are wasteful and ripe for errors. You might want to reconsider the urls that you are presenting to the client, making them more precise so that the rewrite rules can be cleaner, or in

Re: [users@httpd] E-commerce Rewrite Rule

To add to the last response, consider using FallbackResource too, or multiviews if the paths can be translated directly to a file. On Wed, Feb 14, 2018 at 2:50 PM, Richard wrote: > You seem to be making the "urls" that the client gets unnecessarily > complex

RE: [users@httpd] Apache httpd directory listing no longer working

I've found and fixed the problem. It was caused by adding support for php. The following rule caused the problem and is now commented out: DirectoryIndex index.php Thx for helping me with the search for the problem. Regards Stefaan Dutry Van: