Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 45 for communication (0.07 sec)

  1. docs/en/docs/tutorial/cors.md

    Then, the browser will send an HTTP `OPTIONS` request to the `:80`-backend, and if the backend sends the appropriate headers authorizing the communication from this different origin (`http://localhost:8080`) then the `:8080`-browser will let the JavaScript in the frontend send its request to the `:80`-backend.
    
    To achieve this, the `:80`-backend must have a list of "allowed origins".
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Sun Aug 31 09:15:41 UTC 2025
    - 5.5K bytes
    - Viewed (0)
  2. LICENSE

          means any form of electronic, verbal, or written communication sent
          to the Licensor or its representatives, including but not limited to
          communication on electronic mailing lists, source code control systems,
          and issue tracking systems that are managed by, or on behalf of, the
          Licensor for the purpose of discussing and improving the Work, but
          excluding communication that is conspicuously marked or otherwise
    Registered: Sun Sep 07 03:35:12 UTC 2025
    - Last Modified: Wed Sep 11 20:39:30 UTC 2013
    - 11.1K bytes
    - Viewed (0)
  3. docs/en/docs/tutorial/security/index.md

    ### OAuth 1 { #oauth-1 }
    
    There was an OAuth 1, which is very different from OAuth2, and more complex, as it included direct specifications on how to encrypt the communication.
    
    It is not very popular or used nowadays.
    
    OAuth2 doesn't specify how to encrypt the communication, it expects you to have your application served with HTTPS.
    
    /// tip
    
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Sun Aug 31 10:49:48 UTC 2025
    - 4.4K bytes
    - Viewed (0)
  4. docs/en/docs/deployment/https.md

    Then, using the certificate, the client and the TLS Termination Proxy **decide how to encrypt** the rest of the **TCP communication**. This completes the **TLS Handshake** part.
    
    After this, the client and the server have an **encrypted TCP connection**, this is what TLS provides. And then they can use that connection to start the actual **HTTP communication**.
    
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Sun Aug 31 19:34:08 UTC 2025
    - 14.3K bytes
    - Viewed (0)
  5. CREDITS

          means any form of electronic, verbal, or written communication sent
          to the Licensor or its representatives, including but not limited to
          communication on electronic mailing lists, source code control systems,
          and issue tracking systems that are managed by, or on behalf of, the
          Licensor for the purpose of discussing and improving the Work, but
          excluding communication that is conspicuously marked or otherwise
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Thu Mar 13 05:29:51 UTC 2025
    - 1.8M bytes
    - Viewed (0)
  6. apache-maven/src/main/appended-resources/licenses/Apache-2.0.txt

          means any form of electronic, verbal, or written communication sent
          to the Licensor or its representatives, including but not limited to
          communication on electronic mailing lists, source code control systems,
          and issue tracking systems that are managed by, or on behalf of, the
          Licensor for the purpose of discussing and improving the Work, but
          excluding communication that is conspicuously marked or otherwise
    Registered: Sun Sep 07 03:35:12 UTC 2025
    - Last Modified: Tue Jan 28 11:47:17 UTC 2020
    - 11.1K bytes
    - Viewed (0)
  7. CONTRIBUTING.md

    + Fork the repository on GitHub.
    
    Making and Submitting Changes
    --------------
    
    We accept Pull Requests via GitHub. The [developer mailing list][dev-ml-list] is the
    main channel of communication for contributors.  
    There are some guidelines which will make applying PRs easier for us:
    + Create a topic branch from where you want to base your work (this is usually the master branch).
    Registered: Sun Sep 07 03:35:12 UTC 2025
    - Last Modified: Sat Jun 07 09:55:33 UTC 2025
    - 4.2K bytes
    - Viewed (0)
  8. LICENSE

          means any form of electronic, verbal, or written communication sent
          to the Licensor or its representatives, including but not limited to
          communication on electronic mailing lists, source code control systems,
          and issue tracking systems that are managed by, or on behalf of, the
          Licensor for the purpose of discussing and improving the Work, but
          excluding communication that is conspicuously marked or otherwise
    Registered: Sun Sep 21 03:50:09 UTC 2025
    - Last Modified: Mon Jan 11 04:26:17 UTC 2021
    - 11.1K bytes
    - Viewed (0)
  9. LICENSE

          means any form of electronic, verbal, or written communication sent
          to the Licensor or its representatives, including but not limited to
          communication on electronic mailing lists, source code control systems,
          and issue tracking systems that are managed by, or on behalf of, the
          Licensor for the purpose of discussing and improving the Work, but
          excluding communication that is conspicuously marked or otherwise
    Registered: Wed Sep 10 00:11:11 UTC 2025
    - Last Modified: Thu Feb 20 19:53:57 UTC 2020
    - 11.1K bytes
    - Viewed (0)
  10. LICENSE

          means any form of electronic, verbal, or written communication sent
          to the Licensor or its representatives, including but not limited to
          communication on electronic mailing lists, source code control systems,
          and issue tracking systems that are managed by, or on behalf of, the
          Licensor for the purpose of discussing and improving the Work, but
          excluding communication that is conspicuously marked or otherwise
    Registered: Fri Sep 19 09:08:11 UTC 2025
    - Last Modified: Mon Jan 11 04:30:09 UTC 2021
    - 11.1K bytes
    - Viewed (0)
Back to top