
Security News
Static vs. Runtime Reachability: Insights from Latio’s On the Record Podcast
The Latio podcast explores how static and runtime reachability help teams prioritize exploitable vulnerabilities and streamline AppSec workflows.
= clogger - configurable request logging for Rack
clogger is Rack middleware for logging HTTP requests. The log format is customizable so you can specify exactly which fields to log.
== FEATURES
highly customizable with easy-to-read nginx-like log format variables.
pre-defines Apache Common Log Format, Apache Combined Log Format and Rack::CommonLogger (as distributed by Rack 1.0 and 1.1) formats. See Clogger::Format for the predefined formats.
Untrusted values are escaped (all HTTP headers, request URI components) to make life easier for HTTP log parsers. The following bytes are escaped:
' (single quote) " (double quote) all bytes in the range of \x00-\x1F
multi-instance capable and (optionally) reentrant. You can use clogger in a multi-threaded server, and even multiple cloggers logging to different locations and different formats in the same process.
Pure Ruby version for non-MRI versions of Ruby (or via CLOGGER_PURE=1 in the environment). The optional C extension is loaded by default under C Ruby and under Rubinius, too.
== SYNOPSIS
clogger may be loaded as Rack middleware in your config.ru:
require "clogger" use Clogger, :format => :Combined, :path => "/path/to/log", :reentrant => true run YourApplication.new
If you're using Rails 2.3.x or later, in your config/environment.rb somewhere inside the "Rails::Initializer.run do |config|" block:
config.middleware.use 'Clogger', :format => :Combined, :path => "/path/to/log", :reentrant => false
Instead of specifying a :path, you may also specify a :logger object that receives a "<<" method:
use Clogger, :logger=> $stdout, :reentrant => true run YourApplication.new
== VARIABLES
== REQUIREMENTS
== DEVELOPMENT
The latest development happens in git and is published to the following:
git clone https://YHBT.net/clogger.git git clone https://repo.or.cz/clogger.git
You may also browse and download snapshot tarballs:
We use email for coordination and development, see below:
== CONTACT
All feedback (bug reports, user/development discussion, patches, pull requests) is done via publicly-archived email:
Tor users may also access HTTP, IMAP, and NNTP archives via .onion:
AUTH=ANONYMOUS is supported for IMAP and IMAPS, and any username + password will work.
No subscription or real names will ever be required to email us. Do not send HTML email, do not top post.
Homepage: https://YHBT.net/clogger/
== INSTALL
For RubyGems users:
gem install clogger
There is an optional C extension that should be compatible with MatzRuby. The extensions should automatically be disabled for users of other Ruby implementations, but be sure to let us know if that's not the case.
FAQs
Unknown package
We found that clogger demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
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.
Security News
The Latio podcast explores how static and runtime reachability help teams prioritize exploitable vulnerabilities and streamline AppSec workflows.
Security News
The latest Opengrep releases add Apex scanning, precision rule tuning, and performance gains for open source static code analysis.
Security News
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.