| 00:21:32 | | jd_tech joins |
| 02:43:42 | | nostalgebraist joins |
| 03:06:39 | | qw3rty__ joins |
| 03:10:37 | | qw3rty_ quits [Ping timeout: 252 seconds] |
| 04:10:05 | | nostalgebraist quits [Ping timeout: 258 seconds] |
| 04:12:45 | | nostalgebraist joins |
| 04:26:11 | | nostalgebraist quits [Ping timeout: 258 seconds] |
| 04:27:08 | | nostalgebraist joins |
| 06:02:43 | | qw3rty__ quits [Read error: Connection reset by peer] |
| 06:02:55 | | qw3rty__ joins |
| 06:27:36 | | IDK (IDK) joins |
| 07:11:04 | | jodizzle quits [Quit: ...] |
| 07:12:21 | | jodizzle (jodizzle) joins |
| 07:20:25 | | jd_tech quits [Ping timeout: 265 seconds] |
| 07:40:10 | | jd_tech joins |
| 13:35:17 | <[42]> | is it known that https://urlte.am is broken? |
| 13:36:27 | <[42]> | on http it redirects to the tracker (also http), on https it's completely broken |
| 13:58:35 | <gazorpazorp> | http://urlte.am redirects me to the https version of the tracker |
| 14:19:25 | <[42]> | it does not, it redirects you to http://tracker.archiveteam.org:1337/status and that in turn sends you to https://tracker.archiveteam.org:1338/status |
| 14:19:43 | <[42]> | so if you have your browser set to always use https both are broken |
| 14:20:07 | <[42]> | for urlte.am it fails to establish a connection, then if i open :1337 it tries to use https on that port which obviously can't work |
| 14:20:25 | <[42]> | since it's a non-standard port it won't try a different port for the https request |
| 16:04:46 | <@JAA> | I mean, urlte.am doesn't even support HTTPS. |
| 16:04:53 | <klg> | fwiw I don't recall https://urlte.am ever working, but http://urlte.am still works for me in *some* browsers |
| 16:06:08 | <@JAA> | And the redirect works fine for me in Firefox with HTTPS preference (or whatever its proper name is) enabled. It first tries to connect to https://urlte.am/, fails at that, then loads HTTP, and follows the redirect to HTTP 1337 correctly. |
| 16:06:46 | <@JAA> | I do agree that it should redirect to HTTPS directly, but this is a config issue in your browser really. |
| 16:10:51 | <[42]> | JAA: for me it just doesn't work at all with that pref enabled, the fallback doesn't seem to be super reliable |
| 16:13:04 | <@JAA> | [42]: With HTTPS-Only Mode enabled, I need to click 'continue to HTTP site' (or similar) twice, once for urlte.am and once for tracker 1337. With it disabled in a private window, it behaves as above. |
| 16:13:20 | <@JAA> | That latter is a new addition from Firefox 90 or 91 I think. |
| 16:13:46 | <[42]> | Secure Connection Failed |
| 16:13:47 | <[42]> | An error occurred during a connection to urlte.am. PR_END_OF_FILE_ERROR |
| 16:13:55 | <[42]> | that's what i get when i try to open it :( |
| 16:16:27 | <[42]> | in a "clean" firefox nightly profile it works fine though |
| 16:17:00 | <[42]> | may be an issue with my browser but it'd still be nice to have https all the way :) |
| 16:18:38 | <[42]> | also, interestingly closing the private window which i permitted http in does *not* reset that flag for the domain until i restart the browser |
| 16:18:50 | <[42]> | it does not leak to the regular browser session though |
| 16:20:49 | | jd_tech quits [Client Quit] |
| 16:21:28 | <@JAA> | Huh |
| 22:32:43 | | driib0 (driib) joins |
| 22:36:49 | | driib quits [Ping timeout: 265 seconds] |
| 22:36:49 | | driib0 is now known as driib |