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.

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

Please see the project documentation for more details.

• 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.

Please see the project releases for all releases.

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

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

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

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

• Handling of HEAD requests is now more robust.

• 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.

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

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

We welcome contributions to this project.

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

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.

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.

• protocol-http — General abstractions for HTTP client/server implementations.
• async-http — Asynchronous HTTP client and server, supporting multiple HTTP protocols & TLS, which can host the Rack application adapters (and is used by this gem for testing).