Head requests are broken #21

New Issue

electricdusk · 2019-12-09T14:58:16+01:00

electricdusk commented

2019-12-09 14:58:16 +01:00

curl -X HEAD --verbose https://hashru.link/Mt1N
Warning: Setting custom HTTP method to HEAD with -X/--request may not work the 
Warning: way you want. Consider using -I/--head instead.
*   Trying 95.217.81.217:443...
* TCP_NODELAY set
* Connected to hashru.link (95.217.81.217) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: none
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=hashru.link
*  start date: Nov  8 21:28:10 2019 GMT
*  expire date: Feb  6 21:28:10 2020 GMT
*  subjectAltName: host "hashru.link" matched cert's "hashru.link"
*  issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x55b0e4381810)
> HEAD /Mt1N HTTP/2
> Host: hashru.link
> user-agent: curl/7.67.0
> accept: */*
> 
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 405 
< server: nginx/1.16.1
< date: Mon, 09 Dec 2019 13:58:38 GMT
< 
* Connection #0 to host hashru.link left intact

``` curl -X HEAD --verbose https://hashru.link/Mt1N Warning: Setting custom HTTP method to HEAD with -X/--request may not work the Warning: way you want. Consider using -I/--head instead. * Trying 95.217.81.217:443... * TCP_NODELAY set * Connected to hashru.link (95.217.81.217) port 443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /etc/ssl/certs/ca-certificates.crt CApath: none * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.2 (IN), TLS handshake, Certificate (11): * TLSv1.2 (IN), TLS handshake, Server key exchange (12): * TLSv1.2 (IN), TLS handshake, Server finished (14): * TLSv1.2 (OUT), TLS handshake, Client key exchange (16): * TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1): * TLSv1.2 (OUT), TLS handshake, Finished (20): * TLSv1.2 (IN), TLS handshake, Finished (20): * SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 * ALPN, server accepted to use h2 * Server certificate: * subject: CN=hashru.link * start date: Nov 8 21:28:10 2019 GMT * expire date: Feb 6 21:28:10 2020 GMT * subjectAltName: host "hashru.link" matched cert's "hashru.link" * issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3 * SSL certificate verify ok. * Using HTTP2, server supports multi-use * Connection state changed (HTTP/2 confirmed) * Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0 * Using Stream ID: 1 (easy handle 0x55b0e4381810) > HEAD /Mt1N HTTP/2 > Host: hashru.link > user-agent: curl/7.67.0 > accept: */* > * Connection state changed (MAX_CONCURRENT_STREAMS == 128)! < HTTP/2 405 < server: nginx/1.16.1 < date: Mon, 09 Dec 2019 13:58:38 GMT < * Connection #0 to host hashru.link left intact ```

electricdusk added the bug label 2019-12-09 14:58:16 +01:00

electricdusk commented

2019-12-10 00:32:42 +01:00

We should add the HEAD functionality in the render functions in (currently) views.go.

We should add the `HEAD` functionality in the render functions in (currently) `views.go`.

electricdusk referenced this issue from a commit

2019-12-15 07:13:55 +01:00

Respond to HEAD requests Fixes #21

electricdusk closed this issue

2019-12-15 07:13:56 +01:00

electricdusk referenced this issue from a commit

2019-12-15 07:50:08 +01:00