-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow specifying HTTP request parameters #52
Comments
I like this idea. Just don't know how exactly one would pass all the possible header fields to mlc? Via commandarg? |
Probably the best option would be a config file, otherwise it would be impractical to specify different headers for different URLs. See for example: |
I think your pipeline has been hit by this bug:
|
@diegorondini fun fact: It does not fail when I run it locally. Does github somehow prevent requests to github.com from their own runners? You mention missing request parameters? What would that be in this case? |
@becheran I think the first question is why the pipeline checks that link even if there's no such link in the
Returning to this bug,
|
Sorry, I just realized I should have checked out the
|
Ah, right. Did the same mistake and ran it on wrong branch locally 🤦♂️ |
@diegorondini would 'Accept-Encoding: *' help in this case? Might be a sane default since we don't care about the content anyways right now. To make it configurable I think a map of links with wildcards and associated headers would make sense as config parameter. Will think about it. |
@becheran well, not literally:
The official way to mean any encoding should be The library you're using (reqwest?) may support accepting all encodings. Libcurl does that: Not sure though if servers that don't support compression / encoding peacefully decline the "Accept-Encoding" header. |
Yes, I am using reqwest. I did turn on all supported encodings (brotli, gzip, deflate) and that did the trick for now. But I guess there are other cases where a custom request is still required. For example if a authentication token is required for a specific link. |
Is your feature request related to a problem? Please describe.
Some URLs require specific HTTP request parameters.
One example is the github docs pages, for example this
.md
will fail:The reason is that the page requires specific HTTP headers:
community/community#14773
Describe the solution you'd like
It would be nice to have a way to specify HTTP request parameters, possibly per-URL.
The text was updated successfully, but these errors were encountered: