Skip to content

Add protocol configuration option to force HTTP/1 or HTTP/2 - #22

Merged
dblock merged 1 commit into
mainfrom
force-http-protocol-version
Aug 18, 2026
Merged

dblock merged 1 commit into
mainfrom
force-http-protocol-version

Conversation

@dblock

@dblock dblock commented Aug 18, 2026

Copy link
Copy Markdown
Owner

Adds a protocol config option to LinkChecker::Async::HTTP that lets you force the client to use HTTP/1 or HTTP/2, instead of relying on async-http's default protocol negotiation.

LinkChecker::Async::HTTP.configure do |config|
  config.protocol = :http2
end

Also settable per checker instance via LinkChecker::Async::HTTP::Checker.new(protocol: :http1).

Closes #8

  • Updated README with usage docs.
  • Added CHANGELOG entry.
  • Added specs covering :http1, :http2, and invalid protocol values (raises ArgumentError).

LinkChecker::Async::HTTP now supports a protocol config option (:http1 or :http2) that can be set globally via .configure or per checker instance, forcing the client to use a specific HTTP protocol version instead of relying on async-http's default negotiation.

Closes #8

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-actions

Copy link
Copy Markdown
Contributor

Danger Report

No issues found.

View run

@dblock
dblock merged commit 3877e38 into main Aug 18, 2026
10 checks passed
@dblock
dblock deleted the force-http-protocol-version branch August 18, 2026 15:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Configure HTTP versions allowed

1 participant