Add custom HTTP headers support to handle server-side user agent filtering#119
Merged
Add custom HTTP headers support to handle server-side user agent filtering#119
Conversation
Co-authored-by: becheran <22472855+becheran@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix mlc reporting error on valid link
Add custom HTTP headers support to handle server-side user agent filtering
Dec 10, 2025
Co-authored-by: becheran <22472855+becheran@users.noreply.github.com>
Contributor
Author
Fixed in e495e8a. The pipeline was failing due to:
All tests now pass (96 tests total). Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
becheran
approved these changes
Dec 11, 2025
|
@becheran thanks for taking the time to submit this fix. Out of curiosity, what's the best way one could configure headers in the docker container used by the mlc gh-action? |
Owner
|
@eiriktsarpalis try the latest version 1.2.0 which I just released. See the readme on how to pass arguments. You can either write a mlc.toml file for configurations or pass command line args to mlc |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implementation Plan for Custom HTTP Headers
http-headersfield toOptionalConfigstruct inlib.rs--http-headersincli.rsto accept custom headershttp.rsto use custom headers from config when making HTTP requestsSummary
Successfully implemented custom HTTP headers support for mlc. This feature allows users to set custom User-Agent and other HTTP headers to work around issues where servers block requests based on headers.
Pipeline Fixes:
cargo fmtto format code according to project stylehttp_headers: Nonefield to allOptionalConfiginstantiations in test files (end_to_end.rs and end_to_end_mock.rs)All tests now pass successfully (96 tests total).
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.