Skip to content

Allow sending custom headers on fetch method. #259

@aaronfc

Description

@aaronfc

Currently the fetch method is not allowing almost any customization.

I found some webpages in which my requests were blocked because we were not sending the User-Agent header.

To do so, I copy pasted the fetch method and added the curl_setopt($curl, CURLOPT_USERAGENT, 'My User Agent/1.0'); option.

Alternatively, I think that sending an extra header like 'User-Agent: My User Agent/1.0' in the existing CURLOPT_HTTPHEADER option should have worked too.

I could have also done the request by myself and then used the parse method, but fetch includes some extra logic (checking content_type` and making sure the 'url' used is the correct one, that I would have had to replicate.

Proposal:

  • Make it possible to add extra headers (maybe as an optional extra parameter which is [] by default).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions