Shows how to add routes which can serve multiple content types using strict content-type negotiation.
Basically, the Accept header is checked against the list of supplied services and a match found. If there is no
Accept header set in the request, the first service in the list is used. This means that there is NO sophisticated
content negotiation implemented, although Wildcard Accept headers is supported to match the first supplied mapping service.
Linear Supertypes
App, DelayedInit, AnyRef, Any
Ordering
Alphabetic
By Inheritance
Inherited
StrictMultiContentTypeRoute
App
DelayedInit
AnyRef
Any
Hide All
Show All
Visibility
Public
All
Value Members
final def!=(arg0: Any): Boolean
Definition Classes
AnyRef → Any
final def##(): Int
Definition Classes
AnyRef → Any
final def==(arg0: Any): Boolean
Definition Classes
AnyRef → Any
defargs: Array[String]
Attributes
protected
Definition Classes
App
Annotations
@deprecatedOverriding("args should not be overridden", "2.11.0")
Shows how to add routes which can serve multiple content types using strict content-type negotiation. Basically, the Accept header is checked against the list of supplied services and a match found. If there is no Accept header set in the request, the first service in the list is used. This means that there is NO sophisticated content negotiation implemented, although Wildcard Accept headers is supported to match the first supplied mapping service.