Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

DefV-rack_lighttpd_fix

Package Overview
Dependencies
Maintainers
1
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

DefV-rack_lighttpd_fix

  • 0.1.0
  • Rubygems
  • Socket score

Version published
Maintainers
1
Created
Source

= Rack::LighttpdFix

== Why?

On some of the Openminds shared hosting servers we run a Lighttpd+FCGI stack for Ruby/Rails applications. This week we got a complaint from a user saying they had a problem with the latest Radiant 0.8. Every page he loaded was the same as the first page he opened since the last server restart.

When digging into the problem it was clear that it was a problem with Rack::Cache, which only created 1 meta-store entry and served that from there on. On investigation Rack::Cache::Key.call(@request) always returned http://example.com:80/dispatch.fcgi?. Apparently the last part of the key gets created by scriptname and pathinfo:

..snip.. parts << @request.script_name parts << @request.path_info ..snip..

When looking at the request it seems Lighttpd+FCGI doesn't fill in the env['PATH_INFO�], which results in always having the same cache key, thus the same page.

To solve this problem I've created this small Rack middleware gem that sets PATH_INFO from REQUEST_URI (Like Passenger does with Nginx)

== Installation

You can just install this as a gem: gem install -s http://gems.github.com defv-rack_lighttpd_fix

== Configuration for Rails

in production.rb

require 'rack/lighttpd_fix'

config.middleware.insert_before ::Rack::Cache, ::Rack::LighttpdFix

or for Radiant

config.middleware.insert_before ::Radiant::Cache, ::Rack::LighttpdFix

FAQs

Package last updated on 11 Aug 2014

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc