After merging #9, this still didn't work. I found that the reason is the User-Agent header. Since we're emulating a browser, t.co thinks that we are able to parse HTML or run JavaScript, so it's sending us this body:

<head><meta name="referrer" content="always"><noscript><META http-equiv="refresh" content="0;URL=http://bit.ly/berlin-nodejs-meetup"></noscript><title>http://bit.ly/berlin-nodejs-meetup</title></head><script>window.opener = null; location.replace("http:\/\/bit.ly\/berlin-nodejs-meetup")</script>

To be completely honest, it's actually not sending us any body because we're using the HEAD method, but if we were using the GET method it would.

If I change the User-Agent to curl/7.43.0 it now uses a 301 instead.

We added the fake User-Agent on purpose (see 0838baa), so I'm not sure the solution is to remove it again.

One solution might be to change it to a browser that doesn't support JavaScript. For instance Lynx/2.8.8dev.3 libwww-FM/2.14 SSL-MM/1.4.1. That at least fixes it for this URL, but it might add back the issue that was addressed when the User-Agent was introduced.

The other solution is of cause to parse the HTML and use the http-equiv="refresh"

HTTP2 issue? #8

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions