Ben Blackmore

Hey @dsinni, could you describe the use case behind this for me? Preferably with an example app in a PR so that I understand why this needs to be done...

So you are proposing to remove `*/*` from the default `options.htmlAcceptHeaders` configuration? Why is this? Is this coming from an actual problem you are having?

I am well aware of the theory behind this, but so far this library seems to have worked very well for its users. This is why I asked for an...

> Wouldn't a more reasonable solution then be an option to allow for different behavior to resolve this case? That would only mean a minor version, minimal documentation, and no...

No, this doesn't exist, but should be easy to add. Feel free to open a PR and I'll check it out.

This works with express, yes, but please note the different values compared to `req.url` (see the docs).

Hi Joe, this is no longer being actively maintained and AFAIK there are now some issues due to Docker CLI changes :/

Sorry, I don't have a Windows machine. Guess you will need to check this yourself…

Sounds like two good ideas. We should only take care not to put too many `[dock]` labels in front (or maybe to gray them out)? How are we going to...

Just noticed the same thing for the and operator which both other libraries define as whitespace. Example: ``` jsemver: = 4 &