Daenney 9ba35c65eb

[bug] Handle 410 on webfinger properly (#1601) ...

When we receive an HTTP 410 on webfinger it means the resource we asked
for (the account) is gone, but the endpoint itself responded. In such
cases we want to treat the request as successful from a cache (renewal)
point of view, while still returning an error from Finger.

Follow-up for #1588

2023-03-09 10:17:11 +00:00

..

context_test.go

[chore] Update/add license headers for 2023 (#1304)

2023-01-05 12:43:00 +01:00

context.go

[chore] Update/add license headers for 2023 (#1304)

2023-01-05 12:43:00 +01:00

controller.go

[feature] Discover webfinger through host-meta (#1588)

2023-03-08 12:57:41 +00:00

deliver.go

[bugfix] internal server error on search not found (#1590)

2023-03-06 10:38:43 +01:00

dereference.go

[bugfix] internal server error on search not found (#1590)

2023-03-06 10:38:43 +01:00

derefinstance.go

[bugfix] internal server error on search not found (#1590)

2023-03-06 10:38:43 +01:00

derefmedia.go

[bugfix] internal server error on search not found (#1590)

2023-03-06 10:38:43 +01:00

finger_test.go

[feature] Discover webfinger through host-meta (#1588)

2023-03-08 12:57:41 +00:00

finger.go

[bug] Handle 410 on webfinger properly (#1601)

2023-03-09 10:17:11 +00:00

signing.go

[chore] Update/add license headers for 2023 (#1304)

2023-01-05 12:43:00 +01:00

transport_test.go

[feature] Discover webfinger through host-meta (#1588)

2023-03-08 12:57:41 +00:00

transport.go

[bugfix] internal server error on search not found (#1590)

2023-03-06 10:38:43 +01:00