### OAuth 1 { #oauth-1 }

Il y a eu un OAuth 1, très différent d'OAuth2, et plus complexe, car il incluait des spécifications directes sur la manière de chiffrer la communication.

Il n'est plus très populaire ni utilisé de nos jours.

OAuth2 ne spécifie pas comment chiffrer la communication ; il suppose que votre application est servie en HTTPS.

/// tip | Astuce

/// info

Pour envoyer de la donnée, vous devez utiliser : `POST` (le plus populaire), `PUT`, `DELETE` ou `PATCH`.

Envoyer un corps dans une requête `GET` a un comportement non défini dans les spécifications, cela est néanmoins supporté par **FastAPI**, seulement pour des cas d'utilisation très complexes/extrêmes.

        return tookMs;
    }

    /**
     * Returns the list of popular words.
     *
     * @return the list of popular words
     */
    public List<String> getWords() {
        return words;
    }

    /**
     * Returns the number of popular words.
     *
     * @return the number of popular words
     */
    public int getNum() {
        return num;
    }

    /**

                final long lm = f.lastModified();

                if (lm > lastModified) {
                    lastModified = lm;
                    TAB.clear();
                    alt = 0;
                    populate(new FileReader(f));
                }
                result = (NbtAddress) TAB.get(name);
            }
        } catch (final FileNotFoundException fnfe) {
            if (LogStream.level > 1) {

import org.junit.jupiter.api.Tag;
import org.junit.jupiter.api.Test;

import io.restassured.RestAssured;
import io.restassured.path.json.JsonPath;

/**
 * Integration tests for the Popular Words API (/api/v1/popular-words)
 */
@Tag("it")
public class PopularWordsApiTests extends ITBase {

    @BeforeAll
    protected static void initAll() {
        RestAssured.baseURI = getFessUrl();
        settingTestToken();

docs/debugging/hash-set/hash-set
docs/debugging/healing-bin/healing-bin
docs/debugging/inspect/inspect
docs/debugging/pprofgoparser/pprofgoparser
docs/debugging/reorder-disks/reorder-disks
docs/debugging/populate-hard-links/populate-hardlinks
docs/debugging/xattr/xattr
hash-set
healing-bin
inspect
pprofgoparser
reorder-disks
s3-check-md5
s3-verify
xattr

     * so that it may be included in the list of results. IOW we do
     * not want to create a new NbtAddress object for this particular
     * address from which the query is constructed, we want to populate
     * the data of the existing address that should be one of several
     * returned by the node status.
     */

    NodeStatusResponse(final Configuration cfg, final NbtAddress queryAddress) {
        super(cfg);

                    logger.warn("Failed to generate popular words.", e);
                }

                return wordList;
            });
        } catch (final ExecutionException e) {
            logger.warn("Failed to load popular words.", e);
        }
        return Collections.emptyList();
    }

    /**
     * Clears all cached popular word lists.
     */
    public void clearCache() {

  @JvmStatic // Despite being 'internal', this method is called by popular 3rd party SDKs.
  fun invalidatesCache(method: String): Boolean =
    (
      method == "POST" ||
        method == "PATCH" ||
        method == "PUT" ||
        method == "DELETE" ||
        method == "MOVE"
    )

  @JvmStatic // Despite being 'internal', this method is called by popular 3rd party SDKs.
  fun requiresRequestBody(method: String): Boolean =

                        populate(r, tc);
                    }
                }
                result = this.table.get(name);
            }
        } catch (final IOException fnfe) {
            log.error("Could not read lmhosts " + tc.getConfig().getLmHostsFileName(), fnfe); //$NON-NLS-1$
        }
        return result;
    }

    void populate(final Reader r, final CIFSContext tc) throws IOException {