Skip to content
This repository has been archived by the owner on Sep 22, 2023. It is now read-only.

HTTP requests for DIDComm messages should include content type header #223

Open
TimoGlastra opened this issue Jul 16, 2021 · 0 comments
Open

Comments

@TimoGlastra
Copy link
Contributor

In AFJ we filter incoming HTTP requests based on the content-type header. It seems that aries-toolbox does not include any header, meaning the message won't be handled in AFJ.

I've removed the restriction for content-type in my clone of AFJ and that seems to work. We should send the content-type header when sending DIDComm messages over HTTP:

We accept both the old and new one:
V0 = 'application/ssi-agent-wire'
V1 = 'application/didcomm-envelope-enc'

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

1 participant