News for hackers. Stuff that matters.

A comment on Safely Reviving Shared Memory. Parent comment

Re:Safely Reviving Shared Memory by danudey on Tuesday July 21, 2020 @02:21PM (#23909354)
Only in specific situations, where the site is using Apache and has .htaccess files enabled. I would argue that using Apache in the first place is non-optimal, but enabling arbitrary .htaccess files for clients is also a potential disaster.

Then again, I suppose there are enough people out there who just want to FTP up their wordpress code and call it a day, so... ugh.

[ Parent | on HN ]
Re:Safely Reviving Shared Memory by duskwuff on Tuesday July 21, 2020 @06:10PM (#23911523)
WordPress expects a working .htaccess for its URL structure, as do most modern PHP applications. So virtually all shared hosts will support .htaccess.

> I would argue that using Apache in the first place is non-optimal

What would you prefer? nginx is not suited to shared environments at all.

[ Parent | on HN ]
Re:Safely Reviving Shared Memory by john-shaffer on Tuesday July 21, 2020 @07:04PM (#23911873)
> WordPress expects a working .htaccess for its URL structure

I haven't heard this. I'm running WordPress via NGINX with no issues.

[ Parent | on HN ]
Re:Safely Reviving Shared Memory by the8472 on Tuesday July 21, 2020 @03:54PM (#23910303)
If you're only uploading some stuff to wordpress do you need shared array buffers?
[ Parent | on HN ]