Rack application that displays current Git commit information.

Opt in to the future!

Rack::Compress enables Zstd and Brotli compression on HTTP responses

Conditional wrapper for Rack middleware. This is a port of Plack::Middleware::Conditional.

A rack middleware to configure rack env.

Rack middleware rate limiter that provides both time-based limits and quantity-based limits

Middleware that provides both file extension and HTTP_ACCEPT-type content negotiation for Rack applications

Rack::ContentDispositionHelper is Rack middleware that rewrites the decoded filename* directive in the Content-Disposition response header as the value of the filename directive.

Monitoring and logging Content-Length.

Rack middleware for declaratively setting the HTTP ContentSecurityPolicy (W3C CSP Level 2/3) security header to help prevent against XSS and other browser based attacks.

Rack Middleware for setting content type when not provided

It's a rack middleware to validate the header Content-Type of requests.

Implement secure API request igning.

rack convert webp

Logs cookies in rack (eg. rails) applications

A rack middleware library that allows for cookies to be passed through form parameters. Specifically, it merges the specified form parameters into the Cookie header of an http request. It gets around the problem of having a flash application which interacts with a web application that uses cookie based sessions.

Automatically generate REST APIs for Core Data models.

The middleware makes sure any request to specified paths would have been preflighted if it was sent by a browser. We don't want random websites to be able to execute actual GraphQL operations from a user's browser unless our CORS policy supports it. It's not good enough just to ensure that the browser can't read the response from the operation; we also want to prevent CSRF, where the attacker can cause side effects with an operation or can measure the timing of a read operation. Our goal is to ensure that we don't run the context function or execute the GraphQL operation until the browser has evaluated the CORS policy, which means we want all operations to be pre-flighted. We can do that by only processing operations that have at least one header set that appears to be manually set by the JS code rather than by the browser automatically. POST requests generally have a content-type `application/json`, which is sufficient to trigger preflighting. So we take extra care with requests that specify no content-type or that specify one of the three non-preflighted content types. For those operations, we require one of a set of specific headers to be set. By ensuring that every operation either has a custom content-type or sets one of these headers, we know we won't execute operations at the request of origins who our CORS policy will block.

Rack middleware for OAuth2 Provider Server Based on Couchdb

Hit counter Rack Middleware using Memcached