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
The values in the CommonErrorType enum are not valid URI's as specified in RFC 3986.
Shall we correct the URI's to valid URI's as specified in RFC 3986?
URI syntax according to RFC 3986:
The generic URI syntax consists of a hierarchical sequence of components referred to as the scheme, authority, path, query, and fragment. The scheme and path components are required, though the path may be empty (no characters).
The text was updated successfully, but these errors were encountered:
Just to clarify, that i understand the change correctly.
Would be expected that an actual URI is returned, with which the consumer could find further information to the problem that occurred? If that would be the case, it would raise the question, where the problems would be documented?
Actually that is exactly the idea. But I think no one want to implement another error webpage right now. So this is why we will return a empty page.
The documentation must be done by each implementer because the error description might be vary depending on the systems used.
The values in the CommonErrorType enum are not valid URI's as specified in RFC 3986.
Shall we correct the URI's to valid URI's as specified in RFC 3986?
URI syntax according to RFC 3986:
The generic URI syntax consists of a hierarchical sequence of components referred to as the scheme, authority, path, query, and fragment. The scheme and path components are required, though the path may be empty (no characters).
The text was updated successfully, but these errors were encountered: