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

open

opened by

boltless.me 1 month ago targeting master from push-xpolynpvotzt

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>

submitted by

boltless.me 7w 2 comments

diff

expand 1 commit

91d58b44

knotserver: redirect handle-path to did-path

boltless.me 1 month ago

...I hate markdown

boltless.me 1 month ago

ah wait, this doesn't work

resubmitted by

boltless.me 7w 1 comment

diff interdiff

expand 1 commit

e233fe40

knotserver: redirect handle-path to did-path

boltless.me 1 month ago

ready for review! tested https-clone, ssh-clone, ssh-push all still working fine.

resubmitted by

boltless.me 3w 1 comment

diff interdiff

expand 1 commit

57d2cd55

knotserver: redirect handle-path to did-path

oppi.li 1 week ago

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?).

failed to check merge status: invalid xrpc request

Labels

bugfix

assignee

None yet.

Participants 2

AT URI

at://did:plc:xasnlahkri4ewmbuzly2rlc5/sh.tangled.repo.pull/3m3sj67z25x22