title: Content-type for token request in OAuth2
body: <p>Getting curious about <a href="https://www.rfc-editor.org/rfc/rfc6749#section-4.1.1" rel="nofollow noreferrer">https://www.rfc-editor.org/rfc/rfc6749#section-4.1.1</a></p>
  <p>Take a look:</p>
  <blockquote>
  <p>The client constructs the request URI by adding the following<br />
  parameters to the query component of the authorization endpoint URI<br />
  using the &quot;application/x-www-form-urlencoded&quot; format</p>
  </blockquote>
  <p>...and the server has to respond with &quot;application/json&quot;.</p>
  <p>The questions are:</p>
  <ol>
  <li>Why should we use explicitly &quot;application/x-www-form-urlencoded&quot;?</li>
  <li>Are there any obvious benefits from urlencoded?</li>
  <li>What stops me from accepting both urlencoded and json here? Seems, that I am not really violating RFC this way.</li>
  </ol>