Hi,
in the specification for $batch it states that inner request urls can be absolute, relative to the host or relative to the batch request uri.
> The Request-URI of HTTP requests serialized within MIME part bodies can use one of the following three formats:
> Absolute URI with schema, host, port, and absolute resource path.
Example 77:
GET https://host:1234/path/service/People(1) HTTP/1.1
> Absolute resource path and separate Host header.
Example 78:
GET /path/service/People(1) HTTP/1.1
Host: myserver.mydomain.org:1234
> Resource path relative to the batch request URI.
Example 79:
GET People(1) HTTP/1.1
> Services MUST support all three formats.
Currently, Web API supports 77 and 78, but not 79. This is problematic as it causes failures with existing OData clients that try to use that type of urls.
See for example:
http://stackoverflow.com/questions/18813890/post-batch-request-with-breezejs
in the specification for $batch it states that inner request urls can be absolute, relative to the host or relative to the batch request uri.
> The Request-URI of HTTP requests serialized within MIME part bodies can use one of the following three formats:
> Absolute URI with schema, host, port, and absolute resource path.
Example 77:
GET https://host:1234/path/service/People(1) HTTP/1.1
> Absolute resource path and separate Host header.
Example 78:
GET /path/service/People(1) HTTP/1.1
Host: myserver.mydomain.org:1234
> Resource path relative to the batch request URI.
Example 79:
GET People(1) HTTP/1.1
> Services MUST support all three formats.
Currently, Web API supports 77 and 78, but not 79. This is problematic as it causes failures with existing OData clients that try to use that type of urls.
See for example:
http://stackoverflow.com/questions/18813890/post-batch-request-with-breezejs