401 when trying to run graphql query against CDN

I have…

  • [x] Checked the logs and have provided the logs if I found something suspicious there

I’m submitting a…

  • [ ] Regression (a behavior that stopped working in a new release)
  • [x] Bug report
  • [ ] Performance issue
  • [ ] Documentation issue or request

Current behavior

Running graphQL queries against the squidex servers works without a flaw. However when running the same request (with updated URL to match the CDN ofc) against the CDN (we are on the business plan) I get a 401. Token is definitely valid. Happens both when running POST and GET requests.

This is what the CDN returns:

  "traceId": "|30feac0e-476ffafb37889eac.",
  "type": "https://tools.ietf.org/html/rfc7235#section-3.1",
  "statusCode": 401

Expected behavior

CDN doesn’t return 401 when running graphQL request against it.

Minimal reproduction of the problem

Just run a POST or GET request against the CND. Use https://contents.squidex.io/<app>/graphql as URL (maybe that URL is wrong?).


  • [ ] Self hosted with docker
  • [ ] Self hosted with IIS
  • [ ] Self hosted with other version
  • [x] Cloud version

Version: latest


  • [ ] Chrome (desktop)
  • [ ] Chrome (Android)
  • [ ] Chrome (iOS)
  • [ ] Firefox
  • [ ] Safari (desktop)
  • [ ] Safari (iOS)
  • [ ] IE
  • [ ] Edge

Others: Android and Insomnia REST client

Thanks, I will have a look. I can reproduce it.

Can you post all response headers?

I could reproduce the problem locally and will deploy it together with the GraphQL bug.

The reason is a change in the authentication system (not by me).

1 Like

Great, many thanks! :pray:

But please give me the response headers, just to ensure that I have fixed the correct bug.

Of course. Here you go (request has been issued from Insomnia this morning in this case):

content-type: application/json; charset=utf-8
server: Kestrel
accept-ranges: bytes
date: Tue, 25 Aug 2020 10:54:15 GMT
via: 1.1 varnish
x-served-by: cache-fra19161-FRA
x-cache: MISS
x-cache-hits: 0
x-timer: S1598352856.577588,VS0,VE93
content-length: 115

Hi @Sebastian, any idea when this and the graphql fix might go live? We’re eager to release our first app version with Squidex incorporated to our users and this is the only thing left. :slight_smile:

I hope today. Sorry for the delay…

1 Like

it is deployed now and also tested with my test suite :slight_smile:

1 Like

Works like a charm, many thanks! :pray:

1 Like