Project

General

Profile

Feature #1255

API: Content Negotiation

Added by Bernhard Koschiček-Krombholz almost 3 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Bernhard Koschiček-Krombholz
Category:
API
Target version:
5.4.0
Start date:
2020-05-20
Estimated time:

Description

For now, we provide content negotiation with HTTP headers, in a not very professional way, but it works. At the meeting Meeting 2020-05-19, it was ask what we provide and if not a URL pattern negotiation would be better/nicer. Christoph stated, we should stick to one negotiation type, although it is possible to use both, it would be not clear for an application or user.

It is up for discussion.
(very short and simple explaination)

History

#1

Updated by Alexander Watzinger almost 3 years ago

  • Status changed from New to Assigned
#2

Updated by Bernhard Koschiček-Krombholz almost 3 years ago

  • Status changed from Assigned to In Progress

You can access the API now through an HTTPS GET request with a json body (https://redmine.craws.net/projects/uni/wiki/Usage). I hope this will help with the development of the front end.

#3

Updated by Bernhard Koschiček-Krombholz over 2 years ago

  • Status changed from In Progress to Closed

We decided to make the URL patterns, although they are more work for the front end dev, it is the standard way to implement a viewing API. If post/put/delete should be supported, a new discussion should be held.

#4

Updated by Bernhard Koschiček-Krombholz over 2 years ago

  • Target version changed from 208 to 5.5.0
#5

Updated by Alexander Watzinger over 2 years ago

  • Subject changed from Content Negotiation to API: Content Negotiation
#6

Updated by Alexander Watzinger over 2 years ago

  • Target version changed from 5.5.0 to 5.4.0

Also available in: Atom PDF