Protocol::Rack

Provides abstractions for working with the Rack specification on top of Protocol::HTTP. This would, in theory, allow you to run any Protocol::HTTP compatible application on top any rack-compatible server.

Features

Supports Rack v2 and Rack v3 application adapters.
Supports Rack environment to Protocol::HTTP::Request adapter.

Usage

Please browse the source code index or refer to the guides below.

Getting Started

This guide explains how to get started with protocol-rack and integrate Rack applications with Protocol::HTTP servers.

Request and Response Handling

This guide explains how to work with requests and responses when bridging between Rack and Protocol::HTTP, covering advanced use cases and edge cases.

Releases

Please browse the releases for more details.

v0.18.0

Correctly invoke rack.response_finished in reverse order.
Tolerate errors during rack.response_finished callbacks.

v0.17.0

Support rack.response_finished in Rack 2 if it's present in the environment.

v0.16.0

Hijacked IO is no longer duped, as it's not retained by the original connection, and SSLSocket does not support duping.

v0.15.0

Use IO::Stream::Readable for the input body, which is a better tested and more robust interface.

v0.14.0

Handling of HEAD requests is now more robust.

v0.13.0

100% test and documentation coverage.
Protocol::Rack::Input#rewind now works when the entire input is already read.
Protocol::Rack::Adapter::Rack2 has stricter validation of the application response.

v0.12.0

Ignore (and close) response bodies for status codes that don't allow them.

v0.11.2

Stop setting env["SERVER_PORT"] to nil if not present.

Contributing

We welcome contributions to this project.

Fork it.
Create your feature branch (git checkout -b my-new-feature).
Commit your changes (git commit -am 'Add some feature').
Push to the branch (git push origin my-new-feature).
Create new Pull Request.

Developer Certificate of Origin

In order to protect users of this project, we require all contributors to comply with the Developer Certificate of Origin. This ensures that all contributions are properly licensed and attributed.

Community Guidelines

This project is best served by a collaborative and respectful environment. Treat each other professionally, respect differing viewpoints, and engage constructively. Harassment, discrimination, or harmful behavior is not tolerated. Communicate clearly, listen actively, and support one another. If any issues arise, please inform the project maintainers.