{5} Accepted, Active Tickets by Owner (Full Description) (7 matches)

List tickets accepted, group by ticket owner. This report demonstrates the use of full-row display.

adigeo (4 matches)

Ticket Summary Component Milestone Type Created
Description
#123 "Create node" action doesn't check for unique parent node XCAP protocol Future release Defect 07/27/09

Suppose a typical pres-rules document with two rules:

  • id="pres_whitelist"
  • id="pres_blacklist"

If I do a wrong GET: 

GET /xcap-root/pres-rules/users/xcaptest@domain.net/pres-rules/
~~/cp:ruleset/cp:rule/cp:conditions/cp:identity/cp:one

then OpenXCAP replies 404 with body "The requested node selector /cp:ruleset/cp:rule/cp:conditions/cp:identity/cp:one matches more than one element". OK.

But if I do the same in a PUT operation: 

PUT /xcap-root/pres-rules/users/xcaptest@domain.net/pres-rules/
~~/cp:ruleset/cp:rule/cp:conditions/cp:identity/cp:one%5b@id=%22sip:new@new.net%22%5d

then OpenXCAP replies "201 Created" and inserts the commited node into the last <rule>. This is obviously wrong as it should complain.

IMHO, OpenXCAP should perform the same check as in a GET operation before inserting an element.

#113 Validate partial put/delete XCAP server Future release Enhancement 07/12/09

Validation after put/delete attribute

#111 Error formatting XCAP server Next Release Enhancement 07/12/09

Errors from twisted are text/html and from xcap are text/plain: use one (text/plain?)

#117 Check "If-Match" before XML validation Performance Next Release Enhancement 07/16/09

If I upload (PUT) a wrong XML document setting a "If-Match" value which doesn't match the stored value, then OpenXCAP replies "409 Conflict". This means that OpenXCAP validates the XML document before checking the "If-Match" value.

IMHO it would be much better if OpenXCAP inspects first the "If-Match" value, so in the case above it would reply "412" and wouldn't require to validate the content (expensive operation).

saul (3 matches)

Ticket Summary Component Milestone Type Created
Description
#108 Publish xcap-diff XCAP server Next Release Enhancement 07/12/09

Add SIP client support to OpenXCAP to send PUBLISH for xcap-diff event. Modify OpenSIPS to perform refreshWatchers() when the PUBLISH is received.

#119 Implement "application/xcap-error+xml" (and use 409 for errors) XCAP protocol Next Release Defect 07/21/09

According to  http://tools.ietf.org/html/rfc4825#section-11, if a node selection is "invalid" the server should reply 409 with Content-Type "application/xcap-error+xml" and a body following the according XML schema.

But OpenXCAP returns 404 with a description in "text/plain" (for other errors is uses "text/html").

For example: 

HTTP/1.1 404 Not Found
Content-Type: text/plain

The requested node selector
/a:ruleset/a:rule[@id='pres_whitelist']/a:conditions/a:identity/a:one
matches more than one element

The easier issue to handle is to reply 409 in these cases. A more complex task is returing a XML according to section 11 of RFC 4825.

#104 Add "Content-Lenght: 0" to 304 responses Interoperability Next Release Enhancement 07/12/09

I've realized that OpenXCAP doesn't add "Content-Length: 0" when replies 304 (with no body). Sincerelly I'm not sure if Content-Length is required in HTTP even if content size is 0.

However I've detected some HTTP clients getting blocked for some seconds when receving such response, waiting for the body.

Most probably, this is a bug in the client but I suggest OpenXCAP to add "Content-Length: 0" even if body is empty.

Note: See TracReports for help on using and creating reports.