ValidationTool
ValidationTool copied to clipboard
Enable OData service authors ensure that their service interoperates well with any OData client.
Hi, I deployed ValidationTool to localhost. When i input the Uri and click on Validate button. The error message show: "Sending validation request...Retrieving response payload...Error retrieving validation results - please...
http://services.odata.org/validation/
The XHR-specification changed to lowercase all their headers also in HTTP/1.1. Chrome (60) is the first one who changed this, but patches for Gecko/Firefox (https://bugzilla.mozilla.org/show_bug.cgi?id=1370485) and Webkit/Safari are already avaialble
The MinimalConformance100501 rule appears to expect an HTTP 415 in response to a GET request with unknown or unsupported format parameters in the accept header [1]. I don't believe the...
When evaluating a custom built OData service many tests simply report failed. It often takes many attempts at rerunning the specific test with instrumentation of the service being evaluated to...
ODataValidationTool V1.07 #Repro step: 1. Open this page in browser: "http://odatasampleservices.azurewebsites.net/validation/feedback.htm"; 2. Open this page in another tab in browser: "http://services.odata.org/validation/feedback.htm"; # Expect: These feedback pages need sychronized, must be...
With labels: PR_Team: PR submitted by OData team members. PR_Internal: PR submitted by a colleague within Microsoft. PR_External: PR submitted by a GitHub user outside of Microsoft.
ODataValidationTool V1.07 # Repro step: 1. Select "By Uri" tab with following input, press "Validate"; -URI:"http://services.odata.org/V4/(S(ula4o1ze2kawob1zbziqncno))/TripPinServiceRW/" -OData format: JSON-Min -OData Version: OData v4.0 service endpoint 2.After validation complete. # Expect:...
ODataValidationTool V1.07 # Repro step: 1. Select "By Uri" tab with following input, press "Validate"; -URI:"http://services.odata.org/V4/(S(ula4o1ze2kawob1zbziqncno))/TripPinServiceRW/" -OData format: JSON-Min -OData Version: OData v4.0 service endpoint 2. After validation complete. #...
I don't think there is any validation of the DbGeography spec yet. I don't know if Microsofts odata Api returns a valid DbGeography ``` "Geography":{ "CoordinateSystemId":4326, "WellKnownText":"POINT (51.515574 2.025285)", "WellKnownBinary":null...