Search results

After looking at the wiki, is the "magic" rails context arranged so it works with the 404 handler? This would explain my problems with rewrite rules... http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:ruby_rails

I wanted to keep the handy rails context, but handle the rewrites myself (because I wanted to add a check to skip the dispatch rewrite if the URI starts with /images due to lots of missing images on my server). I'd then add my own rewrite rules to route to dispatch.lsapi in the virtual hosts...

default mime type In the Context settings there's a handy 'set default mime type' option. Is this settable on a per-server basis as well?

Forcing a reinstall seems to have fixed the missing-character problem. Strange! There's definitely a bug with the reordering of the contexts though. Frustrating trying to get them in a particular order. + sometimes moves up or down, and changing the order direction confuses things...

Yeah I was just looking into the contexts stuff this morning. What an amazingly powerful area! Litespeed is really pushing the limits on powerful and efficient ways of handling complex webmaster requirements. I was having a bug with the pcre system dropping the first char, so have opened a...

Mac. not sure whether 32 or 64. I tested the latest version and the one before it.

3 Contexts (#1 static, below, #2 dummy one b/c it wouldn't let me sort with jsut two - another bug?, #3 Rails). I've disabled rewrite in my virtual host for testing. Static context exp:^/(login/get_online|feature/box) location: /public/$1 Enable expires: Yes Expires Default: M180 Enable...

Worked great, thanks! last one I promise! 404 images are still calling my rails process, despite my attempts to stop this: RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_URI} !(^/images) RewriteRule ^(.*)$ dispatch.cgi [QSA,L] The logfile shows it matching the !/images, but still...

I haven't been using any .htaccess, just the litespeed rules. Are there rules allowed in .htaccess (besides rewrite ones) that litespeed understands that might help? Thanks!

pre-gzipped files Thanks! I've got another similar question to run by you guys - I'm trying to render a cached file that's already gzipped, but it is automatically saving the file rather than decoding it in the browser. #RewriteCond %{HTTP:Accept-Encoding} .*gzip.* RewriteCond...

It's a static file - I just want to control the expires header information for it on a file-specific level, rather than the default-by-file-type level.

Any way to add it as a header instead?

Awesome, works great! Any tips on the 2nd problem, adding a cache-control header? Are the E- headers just read by litespeed, or can they be added to the header sent to the client? Basically I want to have a custom expiration date for a particular regex of files, where most of them are...

This doesn't seem to be working for me (it is always blank). Should it work? Any suggestions? RewriteCond %{ENV:CACHE_CONTROL} no-cache [NC] RewriteRule . %{REQUEST_URI}?recache [L] Logfile always shows: [REWRITE] Cond: Match '' with pattern 'no-cache', result: -1 Safari dev console...

Didn't use sudo. The config is all in /conf right? lsws ➤ ll conf total 72 drwx------ 2 inspire staff 68 Jan 28 18:20 cert drwx------ 5 inspire staff 170 Jan 28...

Fresh install. Same owner as everything else (my user account). I moved the directory out of the way, installed 4.0.18, and was able to get that working. It seems the main problem was that adding my own virtual host to the listener wasn't overriding the 'example' on the main listener...

I'm surprised no-one else has made this complaint yet since Rails 3 has been out for quite some time, but it seems to not work with the default litespeed settings. Someone has added their own as a custom runner, but I'm not sure how to run it? I guess I can't use the "rails" context type...

This still hasn't been integrated into the official lsapi yet it seems?? :(

I've tried reinstalling several time, restarting, etc. I add a new virtual host, point it to my rails app, add the rails context, delete the 'example' virtual host. Restart it, and the status page still shows the example context listening on the main port, and shows 'reboot required' next to...

Just to clarify, this only works in enterprise edition?