Hi,
It would appear that there is a bug in the way the WebApi batch handlers work. The content of any batched request is null/blank when attempting to access it from a filter.
This is problematic for us as we use filters to check the Content-MD5 header, and therefore require access to the content to perform the check.
Note: The content does become accessible to filters if it is read further upstream, e.g. in a message handler, or a custom batch handler.
I have attached a small project that demonstrates the fault.
Cheers
Ben
It would appear that there is a bug in the way the WebApi batch handlers work. The content of any batched request is null/blank when attempting to access it from a filter.
This is problematic for us as we use filters to check the Content-MD5 header, and therefore require access to the content to perform the check.
Note: The content does become accessible to filters if it is read further upstream, e.g. in a message handler, or a custom batch handler.
I have attached a small project that demonstrates the fault.
Cheers
Ben