You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 25, 2024. It is now read-only.
I'm updating Drupal to the latest version due to recent major security releases and one of the side effects is the organizations API endpoints aren't going to automatically send JSON if no _format is set.
The simple solution is to make sure you have a &_format=json on the API endpoint query string. XML and HAL JSON are also possible, but I'm guessing most folks are going to use json.
I had _format documented, but my example endpoint URLs didn't show it as a required field since the REST service previously defaulted to JSON. It makes sense to require a format, but since it wasn't strictly noted I wanted to manually check with people using the API.
The text was updated successfully, but these errors were encountered:
allella
changed the title
Confirm all REST API calls are defining _format=json
Confirm all REST API calls to the organizations API are defining _format=json
Apr 30, 2018
@Nunie123
I'm updating Drupal to the latest version due to recent major security releases and one of the side effects is the organizations API endpoints aren't going to automatically send JSON if no _format is set.
The simple solution is to make sure you have a &_format=json on the API endpoint query string. XML and HAL JSON are also possible, but I'm guessing most folks are going to use json.
I had _format documented, but my example endpoint URLs didn't show it as a required field since the REST service previously defaulted to JSON. It makes sense to require a format, but since it wasn't strictly noted I wanted to manually check with people using the API.
When Drupal 8 was in beta a couple years ago they also supported the Accept header but they nixed it due to proxy and CDN support reasons.
The text was updated successfully, but these errors were encountered: