Actions
Control Interface » History » Revision 4
« Previous |
Revision 4/40
(diff)
| Next »
Moritz Horsch, 08/06/2012 12:49 PM
Client Activation¶
Interface¶
| URL | http://127.0.0.1:24727/eID-Client |
||
| Method | GET | ||
| Query | tcTokenURL | The URL determines where the client can retrieve the TC Token. See TR-03112-7, section 3.2 | Mandatory |
| ifdName | The ifdName determines the card terminal. | Optional; Not specified yet | |
| contextHandle | Optional; Not specified yet | ||
| slotHandle | The SlotHandle determines a connected eCard. See TR-03112-6, section 3.2.1. | Optional; Not specified yet | |
| Returns | 200 OK | The refresh address is comprised in the Message Body (Hack for Mac OS Safari). | |
| 303 See Other | The Location field in the response should contain the refresh address. | ||
| 400 Bad Request | Malformed GET request, e.g. parameters are missing. | ||
| 500 Internal Server Error | |||
| Content-Types | text/plain | All content should be encoded in text/plain or text/html. text/html |
|
| Notes | |||
TODO * What happens if the Client Activator cannot start an application? * What happens if the Client Activator cannot fetch a TC Token from the given TCTokenURL? Should that result in a 400 or 404?
| URL | http://127.0.0.1:24727/status |
|
| Description | ||
| Method | GET | |
| Query | ||
| Returns | 200 OK | |
| 400 Bad Request | ||
| 406 Not Acceptable | ||
| 500 Internal Server Error | ||
| Content-Types | text/html | Should be used for a HTML website with human readable content. |
| application/xml | Should be used to represent a ConnectionHandle in a machine readable XML format. | |
| application/json | Same as XML but the data should encoded in a JSON format. | |
Updated by Moritz Horsch over 12 years ago · 4 revisions