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
In my scenario, responder support GET_CHUNK and maximum data transfer size is 255 due to transport layer limitation. And then, a requester goes through GET_VERSION and try to send GET_CAPABILITY which without GET_CHUNK.
From responder perspective, it can predict it is likely to hit "ResponseTooLarge" error in upcoming responds (e.g. CERTIFICATE, CHALLENGE_AUTH, MEASUREMENT). Can responder early notify requester with error code that requester capabilities cannot fulfill upcoming transaction?
The text was updated successfully, but these errors were encountered:
Can responder early notify requester with error code that requester capabilities cannot fulfill upcoming transaction?
Yes, but there's not a good error code that conveys that information. Only one that really fits is Unspecified and that's not going to tell the Requester that it needs to support chunking. So you're probably better off waiting for the request and then using ResponseTooLarge.
In my scenario, responder support GET_CHUNK and maximum data transfer size is 255 due to transport layer limitation. And then, a requester goes through GET_VERSION and try to send GET_CAPABILITY which without GET_CHUNK.
From responder perspective, it can predict it is likely to hit "ResponseTooLarge" error in upcoming responds (e.g. CERTIFICATE, CHALLENGE_AUTH, MEASUREMENT). Can responder early notify requester with error code that requester capabilities cannot fulfill upcoming transaction?
The text was updated successfully, but these errors were encountered: