WFS 1.1.0 does not properly handle an ExceptionReport while getting the hit count
Closed this issue · 1 comments
Description
A downstream project encountered a scenario when a WFS server returned an ExceptionReport while getting the hit count. Since it was returning an HTTP 200, the exception mapper configured as a provider in jaxrs did not get triggered.
Steps to Reproduce
Reproducing the error requires a WFS server that returns an error for the hit count, but returns valid records for the results request. I do not have a publicly available WFS server for this.
Expected behavior :
If the hits cannot be determined, then set the hit count to -1 as per the SourceResponse API.
Actual behavior:
The hit count is set to 0.
Reproduces how often:
Always.
Platform and environment:
Mac
Affects versions
2.26.x
Additional Information
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within 7 days. Thank you for your contributions.