Allow setting of headers

[joelgriffith]

https://chromedevtools.github.io/devtools-protocol/tot/Network/#method-setExtraHTTPHeaders

Consumers should probably be allowed to set headers for requests (helps with functional tests so that you can auth once and use headers on subsequent requests).

[schickling]

That's a great idea and could also be used for #29 maybe.

[amjd]

I would second this as well. Support for working with request and response headers is an important feature that's currently missing.

[wade0317]

How could i get the header form chromeless? Now cookie() is available, is there any api for header ?

[gios]

Can we merge this pull request in master and publish this changes with an updated version?

[jahed]

Publish this feature please. It's been almost a month.

[felixfbecker]

@jahed we published lastest master as @sourcegraph/chromeless because we could not have used chromeless with our infrastructure otherwise, feel free to use that.

@schickling is there anything that is blocking this from getting released? That fork has been working fine for us for the past weeks

[jahed]

@felixfbecker no worries, I did the same thing. No point waiting for others when you can do it yourself in the meantime 👍 It turned out chromeless wasn't the solution I needed.

https://www.npmjs.com/package/@jahed/chromeless

[schickling]

@felixfbecker apologies we've been buried in work over the last 2 months. Would you be open to join as a maintainer and cut a release?

[felixfbecker]

Sure. Might not be able to make a big maintenance/time commitment though, but may prep a PR to automate the release process to prevent this in the future :)

[felixfbecker]

@jahed @gios released v1.4.0 (and deprecated our fork)

[jahed]

Cool, I'll delete mine when I get round to it. Think it's safe to close this.