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 Jun 12, 2023. It is now read-only.
We had some issues with mysterious 613 HTTP codes coming back. Urkund support really wanted to see that data packets but there's no facility for this. It would be useful to have a log option to dump the data being sent to urkund at that being returned so that HTTP issues can be investigated.
The text was updated successfully, but these errors were encountered:
interesting idea - the full returned response from the http request should be stored in the table but we're not logging the outgoing data in the same way.
We had some issues with mysterious 613 HTTP codes coming back. Urkund support really wanted to see that data packets but there's no facility for this. It would be useful to have a log option to dump the data being sent to urkund at that being returned so that HTTP issues can be investigated.
The text was updated successfully, but these errors were encountered: