jae

hey, it’s back now, it’s cool, we all need a break now and then, eggbug is no different.

eggbug tripped while carrying a buncha posts! easy there, lil guy

I somehow had the perfect timing to not be affected by this \o/

🖤

i just figured eggbug just needed some time to recover from the post where he was crushed for illustration reasons

just in case this might help, here's a curl log:

❯ curl -Lv cohost.org
*   Trying [2606:4700::6812:15a3]:80...
* Connected to cohost.org (2606:4700::6812:15a3) port 80 (#0)
> GET / HTTP/1.1
> Host: cohost.org
> User-Agent: curl/7.88.1
> Accept: */*
>
< HTTP/1.1 301 Moved Permanently
< Date: Tue, 28 Feb 2023 02:54:44 GMT
< Transfer-Encoding: chunked
< Connection: keep-alive
< Cache-Control: max-age=3600
< Expires: Tue, 28 Feb 2023 03:54:44 GMT
< Location: https://cohost.org/
< Server: cloudflare
< CF-RAY: 7a05e0979c1339da-FRA
<
* Ignoring the response-body
* Connection #0 to host cohost.org left intact
* Clear auth, redirects to port from 80 to 443
* Issue another request to this URL: 'https://cohost.org/'
*   Trying [2606:4700::6812:15a3]:443...
* Connected to cohost.org (2606:4700::6812:15a3) port 443 (#1)
* ALPN: offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: none
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN: server accepted h2
* Server certificate:
*  subject: C=US; ST=California; L=San Francisco; O=Cloudflare, Inc.; CN=sni.cloudflaressl.com
*  start date: Jun  3 00:00:00 2022 GMT
*  expire date: Jun  2 23:59:59 2023 GMT
*  subjectAltName: host "cohost.org" matched cert's "cohost.org"
*  issuer: C=US; O=Cloudflare, Inc.; CN=Cloudflare Inc ECC CA-3
*  SSL certificate verify ok.
* using HTTP/2
* h2h3 [:method: GET]
* h2h3 [:path: /]
* h2h3 [:scheme: https]
* h2h3 [:authority: cohost.org]
* h2h3 [user-agent: curl/7.88.1]
* h2h3 [accept: */*]
* Using Stream ID: 1 (easy handle 0x5586d338dce0)
> GET / HTTP/2
> Host: cohost.org
> user-agent: curl/7.88.1
> accept: */*

it got stuck here for a while, and after sitting there for a minute i got this response:

< HTTP/2 303
< date: Tue, 28 Feb 2023 02:54:14 GMT
< content-type: text/plain; charset=utf-8
< content-length: 37
< x-powered-by: Express
< content-language: en
< vary: Origin, Accept
< access-control-allow-credentials: true
< location: /rc/welcome
< set-cookie: connect.sid=s%3AUrul4AOCDQ38CE-Z6JAprBIQR5r_Rf3A.QDrdJzG%2BsySH%2FI9Gw4%2BWNRDgg7%2BEJiL1kYNNQZ1qlz0; Domain=cohost.org; Path=/; Expires=Tue, 07 Mar 2023 02:53:14 GMT; HttpOnly; Secure; SameSite=Lax
< strict-transport-security: max-age=15724800; includeSubDomains
< cf-cache-status: DYNAMIC
< server: cloudflare
< cf-ray: 7a05de6529093a68-FRA
<
* Ignoring the response-body
* HTTP/2 stream 1 was not closed cleanly: INTERNAL_ERROR (err 2)
* Connection #1 to host cohost.org left intact
curl: (92) HTTP/2 stream 1 was not closed cleanly: INTERNAL_ERROR (err 2)

and judging by the < x-powered-by: Express header, id guess that its either some middleware or the actual cohost code

sorry jae!!