commit 4ed5278621a6fb857a6d5f8c552118def59f3918 parent ddaec876a1c42e79ae202eec660e0298796d34a0 Author: Andrew Laack <andrew@laack.co> Date: Wed, 3 Jun 2026 21:16:43 -0500 Added a note about status codes 10 and 11 Diffstat:
| M | main.go | | | 5 | +++++ |
1 file changed, 5 insertions(+), 0 deletions(-)
diff --git a/main.go b/main.go @@ -95,6 +95,11 @@ func updateSite(newUrl string, reuseNode bool) error { site.statusCode = resp.Status // if statuscode // 10 == 1; show popup for user interaction per 1x status code specification + // TODO: Make this better. Technically, the spec states that status code 10 is for + // inputs and 11 **should** behave like a password field with input masked (emphasis on should) + // so per rfc specifications I don't have to. + // So maybe we should special case both of them to support this and make sure other status codes, + // once we have full coverage are errored? if site.statusCode >= 10 && site.statusCode < 20 { showInputBox = true