[closed] How does RTC redirect an OSLC work item URL to the UI editor for the work item?

When a Jazz application such as Rational DOORS Next Generation has a Requirement that has an implementedBy link to an RTC WorkItem, hovering over the link displays the OSLC resource URI for the work item (in the browser status bar), something like: https://<host>:9443/ccm/resource/itemName/com.ibm.team.workitem.WorkItem/<id>. If you put that URI into Poster and do a GET with the Accept header set to application/rdf+xml, you'll get back and RDF representation of the work item resource.

However, if you do a GET with Accept set to application/html, you get 406 Not Acceptable.

When a user clicks on the work item link in RDNG however, or if you paste the work item OSLC URI into the browser's address window, you will be redirected to the RTC UI for the work item, something like: https://<host>:9443/ccm/web/projects/Low%20Flow%20Washer%20%28Change%20Management%29#action=com.ibm.team.workitem.viewWorkItem&id=3

How is this redirection done? What headers are required to tell RTC to redirect to the work item UI and not attempt to generate a pretty HTML version of the RDF resource? What is the protocol convention for dealing with single sign-on?