knotserver: redirect handle-path to did-path #705

fixing issue reported on discord: https://discord.com/channels/1361963801993285692/1361966362653757450/1430609124114301060

knotserver: redirect handle-path to did-path

this will allow handle based url when cloning from knot over https
usually appview will resolve this before redirecting to the knot

this implementation just redirects to resolved path instead of passing
the entire identity for performance. As we won't want to resolve same
identity twice when proxied by appview.

Signed-off-by: Seongmin Lee <git@boltless.me>

1 changed file

Interdiff #1 → #2

expand all

unified split

knotserver

router.go

knotserver/router.go

This patch was likely rebased, as context lines do not match.

History

3 rounds 6 comments

boltless.me submitted #2 3mo

diff

1 commit

expand

57d2cd55

knotserver: redirect handle-path to did-path

3/3 success

expand

expand 3 comments

oppi.li 3mo

will give this a test locally; but that being said, the knotserver need not provide the full API layer that the appview provides. but IMO this one is pretty nice to have (maybe we want all the rerouting rules in that case?).

boltless.me 7w

closing for https://tangled.org/tangled.org/core/pulls/1001

boltless.me 7w

oops wrong PR, can't remove the comment yet.

pull request successfully merged