Make automatic HEAD -> GET configurable

[dougwilson]

The automatic conversion of HEAD requests to GET requests when there is no HEAD method in the route should be configurable (i.e. turn it on or off).

[defunctzombie]

Sounds like a router setting. 👍

[rsandor]

This behavior is not very clear (using 4.12.2). Take for example, registering routes in this order:

app.get('/resource/:id', getHandler);
app.head('/resource/:id', headHandler);

Done this way you will never ever hit the headHandler. However, if you reverse the order:

app.head('/resource/:id', headHandler);
app.get('/resource/:id', getHandler);

The headHandler is called on HTTP HEAD requests, and the getHandler is called on GET. Caused me a headache today 👎

[dougwilson]

@rsandor yes, this is a sad situation :( This is one of the reasons we added .route() to Express 4.0, though, so you won't ever hit this issue:

app.route('/resource/:id')
.get(getHandler)
.head(headHandler)

[dougwilson]

As a bonus, using .route() is more efficient, so you'll have a slightly higher throughput for the equivalent non-.route() app.

[Neta-Alon]

Sorry to bump an old issue - Is .route() always preferred, or just in situations where you have a single URL with a few HTTP methods?
Is it more efficient just in general?

[dougwilson]

It is always preferred and more efficient in general, due to the stack being more compact.

[rsandor]

@dougwilson - Are the use of routes now enforced at an interface level in the newest versions of the library? If not, I highly suggest either making them so or simply fixing this issue. It seems like bad form to let a problem like this persist :/

[dougwilson]

@rsandor , you're welcome to express your displeasure of the pace of this project to callback@strongloop.com , as this project is under StrongLoop and I am just a Collaborator.

[rsandor]

@dougwilson - kudos for not answering my question and taking the critique as a personal attack. Sorry I confused you with someone who could have an impact on the project.

[dougwilson]

No problem!