You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In some instances, it's desirable to add custom request headers. Please consider adding headers to the WebpageOptions struct which can then be passed to the Easy handle in HTTP::fetch
The text was updated successfully, but these errors were encountered:
Apologies for the delay in response. I agree this is definitely a useful feature.
Adding a new field to the all-pub WebpageOptions is a breaking change unfortunately, but I don't mind moving to a v2 version.
To avoid further backward incompatible additions to the struct we should probably mark it with #[non_exhaustive].
Is this something you would be willing to draft a PR for? I could do it myself but maintenance of this crate is not my top priority to it might take a while.
Thanks for the work on this one.
I have just released v2.0.0-alpha.1 so you can use this in your projects.
I'm considering some other breaking changes before I release the official v2
In some instances, it's desirable to add custom request headers. Please consider adding
headers
to theWebpageOptions
struct which can then be passed to the Easy handle inHTTP::fetch
The text was updated successfully, but these errors were encountered: