the event server should handle a SUBSCRIBE request with an absolute URI and not
return a 400
--------------------------------------------------------------------------------------------
Key: FELIX-1859
URL: https://issues.apache.org/jira/browse/FELIX-1859
Project: Felix
Issue Type: Improvement
Components: UPnP Subproject
Reporter: Frank Scholz
Priority: Minor
when sending an event subscription request like this:
SUBSCRIBE http://192.168.1.1:4004/service/0/event HTTP/1.1
HOST: 192.168.1.1:4004
TIMEOUT: Second-1800
CALLBACK: <http://192.168.1.1:47552/events>
NT: upnp:event
Felix answers with an "HTTP/1.1 400 Bad Request" response.
Sending the SUBSCRIBE request with the publisher path part '/service/0/event'
only,
as in
SUBSCRIBE /service/0/event HTTP/1.1
results in a working event subscription.
This corresponds to the example given in chapter "4.1.1 Eventing: Subscribing:
SUBSCRIBE with NT and CALLBACK" of the UPnP Device Architecture 1.0 (or 4.1.2
in the 1.1 Device Architecture).
Please notice the change from "single relativ" to "single absolute" path there.
Nevertheless RFC 2616 states in "5.1.2 Request-URI" [1] that
The Request-URI is a Uniform Resource Identifier (section 3.2) and identifies
the resource upon which to apply the request.
Request-URI = "*" | absoluteURI | abs_path | authority
[....]
To allow for transition to absoluteURIs in all requests in future versions of
HTTP, all HTTP/1.1 servers MUST
accept the absoluteURI form in requests, even though HTTP/1.1 clients will
only generate them in requests to proxies.
Therefore it would make sense to accept all relevant Request-URI variants.
[1]: http://www.w3.org/Protocols/rfc2616/rfc2616-sec5.html#sec5.1
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
