Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(#702): Readiness logic cannot access APIs when custom allowed origins are set #704

Commits on Oct 22, 2024

  1. Configuration menu
    Copy the full SHA
    0bb876e View commit details
    Browse the repository at this point in the history
  2. Merge branch 'dev' into 702-readiness-logic-cannot-access-apis-when-c…

    …ustom-allowed-origins-are-set
    
    # Conflicts:
    #	evita_common/src/main/java/io/evitadb/utils/NetworkUtils.java
    #	evita_external_api/evita_external_api_graphql/src/main/java/io/evitadb/externalApi/graphql/GraphQLProvider.java
    #	evita_external_api/evita_external_api_lab/src/main/java/io/evitadb/externalApi/lab/LabProvider.java
    #	evita_external_api/evita_external_api_observability/src/main/java/io/evitadb/externalApi/observability/ObservabilityProvider.java
    #	evita_external_api/evita_external_api_rest/src/main/java/io/evitadb/externalApi/rest/RestProvider.java
    #	evita_external_api/evita_external_api_system/src/main/java/io/evitadb/externalApi/system/SystemProvider.java
    #	evita_functional_tests/src/test/java/io/evitadb/server/EvitaServerTest.java
    lukashornych committed Oct 22, 2024
    Configuration menu
    Copy the full SHA
    e3515a7 View commit details
    Browse the repository at this point in the history