Skip to main content
replaced https://tools.ietf.org/html/rfc with https://www.rfc-editor.org/rfc/rfc
Source Link

No, it is not acceptable.

In many cases communication within The OAuth 2.0 Authorization FrameworkThe OAuth 2.0 Authorization Framework TLS is shown a "MUST" (required) or "SHOULD" (which implies RECOMMENDED)

No, it is not acceptable.

In many cases communication within The OAuth 2.0 Authorization Framework TLS is shown a "MUST" (required) or "SHOULD" (which implies RECOMMENDED)

No, it is not acceptable.

In many cases communication within The OAuth 2.0 Authorization Framework TLS is shown a "MUST" (required) or "SHOULD" (which implies RECOMMENDED)

Removed fluff
Source Link
user163495
user163495

NONo, it is not acceptable. In

In many cases communication within The OAuth 2.0 Authorization Framework TLS is shown a "MUST" (required) or "SHOULD" (which implies RECOMMENDED) -jim

NO it is not acceptable. In many cases communication within The OAuth 2.0 Authorization Framework TLS is shown a "MUST" (required) or "SHOULD" (which implies RECOMMENDED) -jim

No, it is not acceptable.

In many cases communication within The OAuth 2.0 Authorization Framework TLS is shown a "MUST" (required) or "SHOULD" (which implies RECOMMENDED)

Source Link
jwilleke
  • 251
  • 1
  • 6

NO it is not acceptable. In many cases communication within The OAuth 2.0 Authorization Framework TLS is shown a "MUST" (required) or "SHOULD" (which implies RECOMMENDED) -jim