Skip to content

CORS and concurrency #59

@mDomingues

Description

@mDomingues

Hi guys,
I've been using echo for a while and its awesome. Congratz. 👍

My bundle has a front-end application that requests data from an API with echo. When the load of requests is too high, sometimes I receive a HTTP 502 error due a >> No 'Access-Control-Allow-Origin' header is present on the requested resource. <<
I use rs/cors middleware as found in the docs.

The headers are well-formed as it is supposed to be.
Between client and Go API there is a cloudflare-nginx server.

What are you're guess about this ? Has Echo any kind of issue regarding concurrent requests ? Like that ones "Response headers were already written" ?

I can reproduce this error if I kill the API service. Response from server is the same. It seems a concurrency problem..

Thank you so much for your help. :)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions