Update authorizing-oauth-apps.md

[lopo12123]

Why:

I found that this request should be GET instead of POST, so I made this change

Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

• A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
• The changes in this PR meet the docs fundamentals that are required for all content.
• All CI checks are passing and the changes look good in the review environment.

[welcome]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[github-actions]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source	Review	Production	What Changed
apps/oauth-apps/building-oauth-apps/authorizing-oauth-apps.md	fpt ghec ghes@ 3.17 3.16 3.15 3.14	fpt ghec ghes@ 3.17 3.16 3.15 3.14

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

[Sharra-writes]

@lopo12123 Thanks for opening a PR! Could you do me a favor and give me a little more context on why this change should be made? I need to be able to accurately summarize the problem for our SMEs when I go to ask for verification, and this is not my area of expertise. Any error messages you might have received would be helpful!

[lopo12123]

This request needs to use GET, not POST. The documentation says POST, which is misleading, so I hope to correct the error in the description in a timely manner.
By the way, it was only after trying POST several times that I finally figured out how to use GET that it worked.

[Sharra-writes]

@lopo12123 Our SMEs tell me that GET was supported in the OAuth 1.0a spec, but is no longer supported in the 2.0 spec. It may work for you because you're using an older spec, but POST is correct for the current spec.

[m-balghonaim]

👋🏽 @lopo12123, thank you for helping us keep our docs up to date!

You should be able to use POST for this request. There might be a configuration issue with your POST request if it's not succeeding.