Search results

the value there is already 120 the user is reporting that he got the error in much shorter than 120 seconds.

which value should I adjust to increase the time-out value? a user is complaining that he gets this error a lot when he try to upload multiple images on his forum.

actually, i got it working now. it seems eaccelerator was caching the phpinfo page makes the values don't change. :( my bad thanks for the help.

directadmin yah i checked phpinfo() and the php value didn't change.

it's already like that in my server config. .htaccess is working, it's just can't change the php values using .htaccess

i'm using the same php.ini from my apache configuration, was able to control php values when using apache, but after switching to litespeed, can't do that anymore, is there a setting in litespeed I missed?

not sure why doesn't seem to work, tried php_value register_globals on in .htaccess doesn't work, but other stuff like redirect works.

when we have apache, mod_php, we used to be able to control php values like register_globals use .htaccess, makes it very handy for hosting users, now after switching to litespeed, this no longer works, is there a way to make it work? some users need to change the values before their application...

oh, I thought the vps edition is just limited to 500 connections.

Does the VPS edition works with dedicated server?

Thanks for your reply!!!

If the client is behind multiple transparent proxies with x-forwarded-for header, does lsws still able to see the real IP? Is this feature only available in Enterprise version?

so this feature only log the the client's real ip, what about the other functions like php scripts, do they see the real ip as well? mod_rpaf makes everything sees the real ip.