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 May 24, 2022. It is now read-only.
When a rule owner does not get the expected result from ORM, it is currently difficult to identify why this is happening. A debug feature that sets one or more headers, identifying the namespace/rule that the request matched, would be very helpful in these cases.
The debug feature should not be publicly available and preferably activated by including an appropriate header in the request. For example, if we set "X-ORM-DEBUG: True" the response should include the debug headers identifying the matching rule.
(imported from internal bug-tracker)
The text was updated successfully, but these errors were encountered:
When a rule owner does not get the expected result from ORM, it is currently difficult to identify why this is happening. A debug feature that sets one or more headers, identifying the namespace/rule that the request matched, would be very helpful in these cases.
The debug feature should not be publicly available and preferably activated by including an appropriate header in the request. For example, if we set "X-ORM-DEBUG: True" the response should include the debug headers identifying the matching rule.
(imported from internal bug-tracker)
The text was updated successfully, but these errors were encountered: