You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 22, 2023. It is now read-only.
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'
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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'
The text was updated successfully, but these errors were encountered: