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

graphql endpoint fails pre-flight checks #30298

Closed
wezell opened this issue Oct 8, 2024 · 2 comments · Fixed by #30299
Closed

graphql endpoint fails pre-flight checks #30298

wezell opened this issue Oct 8, 2024 · 2 comments · Fixed by #30299

Comments

@wezell
Copy link
Contributor

wezell commented Oct 8, 2024

Parent Issue

No response

Problem Statement

When we try to use the graphql endpoint from browser js, it throws a 400 on the OPTIONS method and thus fails the pre-flight checks. You can see it failing here: https://www.dotcms.com/playgrounds/graphql/

Access to fetch at 'https://demo.dotcms.com/api/v1/graphql' from origin 'https://www.dotcms.com/' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: It does not have HTTP ok status.

Steps to Reproduce

Open your network tab try this page - it is failing:

https://www.dotcms.com/playgrounds/graphql/

Acceptance Criteria

head to this site:
https://studio.apollographql.com/sandbox/explorer/?referrer=docs-content

and point the explorer to your local instance, e.g. https://local.dotcms.site:8443/api/v1/graphql

and make sure the graphql calls are working

dotCMS Version

24.09

Proposed Objective

Technical User Experience

Proposed Priority

Priority 2 - Important

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

wezell added a commit that referenced this issue Oct 8, 2024
…a 400 before and failing - meaning graph was not working on the client side.

ref: #30298
wezell added a commit that referenced this issue Oct 8, 2024
…a 400 before and failing - meaning graph was not working on the client side.

ref: #30298
@nollymar nollymar moved this from New to In Review in dotCMS - Product Planning Oct 9, 2024
@nollymar nollymar removed the Triage label Oct 9, 2024
@github-project-automation github-project-automation bot moved this from In Review to Internal QA in dotCMS - Product Planning Oct 9, 2024
@nollymar nollymar reopened this Oct 9, 2024
@github-project-automation github-project-automation bot moved this from Internal QA to Current Sprint Backlog in dotCMS - Product Planning Oct 9, 2024
@nollymar nollymar moved this from Current Sprint Backlog to Internal QA in dotCMS - Product Planning Oct 9, 2024
@dcolina dcolina self-assigned this Oct 14, 2024
@dcolina
Copy link
Contributor

dcolina commented Oct 14, 2024

Internal QA: Passed.

The issue couldn't be reproduced anymore. It was tested using the docker imagen dotcms/dotcms:trunk_9a1866f.

Screen.Recording.2024-10-14.at.16.19.27.mov

@dcolina dcolina closed this as completed Oct 14, 2024
@dcolina dcolina moved this from Internal QA to QA - Backlog in dotCMS - Product Planning Oct 14, 2024
@dcolina dcolina removed their assignment Oct 14, 2024
@bryanboza
Copy link
Contributor

Fixed, tested on the latest trunk // Docker // FF

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

4 participants