{5} Assigned, Active Tickets by Owner (Full Description) (4 matches)
List tickets assigned, group by ticket owner. This report demonstrates the use of full-row display.
serialseb (4 matches)
| Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #20 | The codec matching algorithm should support additional media type matching | Core - Codec Support | 2.1 Beta 1 | enhancement | 01/10/09 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
There are a couple of cases not covered with the conneg validation.
This is necessary for managing fallback to application/octet-stream or text/plain when the media type is unknown, and for the case where an xml base type is associated with a base xml type (see #18). |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #12 | Vary header is not updated correctly | Core - Codec Support | 2.0 | defect | 12/04/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The Vary header is not correctly updated when conneg happens. Work involved:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #111 | Problems with query string "unescaping" spaces | Core - Uri Processing | 2.1 Beta 1 | defect | 09/15/09 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
In UriTemplate?.cs when unescaping the uri data string (in the ParseQueries? method), the method uses Uri.UnescapeDataString? from the System namespace. This method does not convert '+' in the uri to spaces, which means any query string parameters with spaces come through to the matched method with a '+' sign instead. From the MSDN documentation for Uri.UnescapeDataString?, "Many Web browsers escape spaces inside of URIs into plus ("+") characters; however, the UnescapeDataString? method does not convert plus characters into spaces because this behavior is not standard across all URI schemes.". It's quite annoying to have to convert all '+' signs to spaces in the matching method, and also inaccurate as if the query string contains %2B, uri.unescapedatastring correctly converts that to a '+' symbol. I think the right call is to run value.replace('+',' ') before passing to Uri.UnescapeDataString?. This problem still exists in trunk. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #119 | Add support for Unity as a container. | Core - DependencyInjection | enhancement | 10/23/09 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Patch attached, details discussed in mailing list. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
