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

Timeout on OPTIONS (cors preflight) #383

Open
robertocarvajal opened this issue Nov 24, 2024 · 2 comments
Open

Timeout on OPTIONS (cors preflight) #383

robertocarvajal opened this issue Nov 24, 2024 · 2 comments
Assignees

Comments

@robertocarvajal
Copy link

robertocarvajal commented Nov 24, 2024

Seems like the mediator is responding like this:

atala-prism-mediator-identus-mediator-1  | 2024-11-24_00:56:53.696 WARN  f.d.f.TransportDispatcher@L167:[ZScheduler-Worker-1] {version=1.0.0, msg_sha256=c4946137e7ddb36a3261fd6dfb6b0b4265280b0a3dfc91c3e449513dd2c7ed10} - zio-fiber-1940542155 No url to send message
o.h.i.m.DIDCommRoutes@L167:[ZScheduler-Worker-2] {version=1.0.0} - zio-fiber-1688384339 Request Timeout

For a CORS check from the browser, this is causing Safari 18 to stop polling the endpoint since it triggers a CORS failure

Other browsers seems to just ignore this timeout and work fine.

In order for this bug to reproduce you need to run Safari 18 (Sequoia) on mediator v1.0.0.

@FabioPinheiro
Copy link
Contributor

I'm having difficulties replicating with Safari Version 18.1.1 (20619.2.8.11.12)

Are you using local environment? Is it a public one that I can use?
Do you have any proxy or are you calling the service directly?
What DIDComm protocol are you using?
Are you using the WebSocket or just the a POST?

@FabioPinheiro FabioPinheiro moved this from In Progress to QA in Hyperledger Identus - Roadmap Dec 9, 2024
@coveloper
Copy link

DIDComm v2. No Websockets.

It was public but we blocked Safari on detection since it fails.

I will remove the block and attach more real world data.

Can show you the issue on a 1x1 call as well if that helps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants