Search results

Hi, I'm tryign to define a new MIME type for Atom Publishing Protocol Entry documents which have a content type of "application/atom+xml;type=entry" So in the mime.conf file I add entry = application/atom+xml;type=entry but after restarting lsws, I get a warning [MIME] File...

Yep, I came up with a similar solution. I was creating an lsapi external app for use by an LSAPI context (using http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:ruby_rails) thinking that might be more flexible and in doing so I ended up adding the following rewrite rules to...

Hi, I have a rails application that is set up to cache pages for certain URLs for lsws to serve (when they exist) without hitting the rails application. Most of these URLs represent RESTful rails resource (i.e. using map.resource in routes.rb and restful controller implementations). An...

I think that's the crux of the problem. If litespeed allowed that behavior to be configurable (via a rails context config option, defaulting to 'public') then I'd be able to manually set it to 'public/v1' and I suspect that would get it all working. Any chance of adding such a config option...

Hmmm, it is a bit of a hack isn't it - I'd be concerned that every request will end up having to go through the same hoop. (I'm also not that proficient at writing apache rewrite rules) One a more general note though, do you think this is a bug or am I wrong to assume this should work? i.e...

I don't think this is possible as the rails caches_page: impl uses the routes config to figure out the correct path for the resource. Also, this is only one example - i'll likely have many cachable resources in each context. I'd probably do this, if I knew how :) Would I loose anything by...

Is the document root actually used at all for these requests (when the context is a rails context)? I've tried tinkering with it, setting it to various filesystem paths (/trunk/app/public, trunk/app/public/v1 etc) but it seems to have no effect on the request dispatching at all...

Rails is creating the cached files under /trunk/rails1/public . For example, when generating '/v1/groups.atom', rails places the cached file at /trunk/rails1/public/v1/groups.atom. (note, the rails app is 'aware' of the 'v1/' part of the url path - it is prefixed to all rails routes) The...

Hi all, I have several rails apps running under a single vhost under contexts like '/v1', '/v2', '/v3' - all work fine with no page caching enabled. When I enable page caching for some actions, rails is correctly generating the cache files in <RAILS_ROOT>/public (or whatever dir I set...