Search results

Hi Enthess, There is no direct way to modify response headers, unfortunately. When it comes to the Date header specifically, that is added at the very end, so that specific header is not modifiable. That said, we have a module system in beta in OLS. What this does is it allows you to hook...

Hi enthess, We do not have an xdebug package for any lsphp versions. That said, I've read that there are issues with installing xdebug via package managers, so if you're willing to try, you could try installing xdebug from source. The few things to note when using lsphp vs regular php: 1...

Date, Connection, and possibly Expires will be set by OLS. Not sure about much else, but I can always ask the relevant dev if you have any specific q's :)

As I mentioned in the other thread, there is not much time left to debug this today. Just know that we are still working on debugging this issue.

I do not have time to further test this tonight, but what does your config look like? Is the custom 404 page the only custom error page listed? Or do you have multiple custom pages? I did a quick test on 1.4.21, and it did not fail, so it may be a recent change.

So you added your custom error page there, but it's not reporting 404? We will take a look.

Hi AEDELGOD, In the web admin, go to Virtual Hosts->Your vhost->General. There is a customized error pages section. Is this what you're looking for? Cheers, Kevin

Hi Alex, In the rewrite section, you should be able to input something like: rewriteFile /path/to/rewrite/file Let me know how it goes, Kevin

Hey there, We are able to reproduce this issue in our lab. I'll let you know of any progress. Cheers, Kevin

Hi AEDELGOD, Could you provide the steps for how you installed OLS? We will try to reproduce the problem in our lab. Kevin

Hi makcode, Thanks for the kind words! In the rewrite rule section of the vhost configurations, please set rewrite logging to '9'. Then, when you access the relevant pages, you will be able to see what was compared in the log. If it's still unclear, send me the log and I'll be happy to help...

Hi Enthess, DOC_ROOT is simply not defined yet at that point :) DOC_ROOT is associated with virtual hosts, so it will not be defined for the server level. Hope this helps, Kevin

Hi riodanzero, Apologies for the late reply. Do you mean how to point a domain and subdomain to a virtual host? If so, please try this out. Let me know how it goes, Kevin

Hi Enthess, We do not believe that OLS is the root cause of this problem. Can you provide the steps/pages accessed to reproduce the issue? Kevin

Here's a general guide. Unless you were able to install lsphp on windows (I don't think we provide that :D), you'll be looking at a fastcgi app possibly instead of LSAPI.

If you go to wherever you added the rules and set the rewrite logging to 9 and restart the server, it should explain how it fails, what it tried to match. The $ is used to mean "ends with", so using my rule as an example, it means "ends with wp-login.php"

So obviously ols wasn't built to be used on Windows, so I'm not sure if lsphp will work. One idea you could try is to install a windows based php binary and see if you can point ols to it? Adding it as an ext app.

Hi Indrek, Try something like this: RewriteCond %{HTTP:CF-IPCOUNTRY} !^(US|CA)$ RewriteRule wp-login.php$ - [F,L]

What did you want to do with that rule? It looks like it's doing what the rule should be doing, it's matching ^ and converting it to 0.php. Did you intend to do something different?

Hi slowaways, The first two lines are not needed. You will have to put this in the virtual host's rewrite rules. This can be done via web admin at Virtual Host -> select virtual host -> Rewrite This can also be done by editing your virtual host's config file...