Bug:401 Unauthorized status in Chrome Log

[nikoids]

When the user is not authorized, 401 status appears in the logs every time; after the user is authorized, this status disappears.
How can I prevent the 401 status from being shown to visitors in console.logs?

[OthyTenk]

Yes. Also, it affected my performance issues to me.

[theodesp]

Hey @OthyTenk and @nikoids . Those errors you are seing are originated from the Browser and the framework doesn't control this API nor does it emit this kind of messages.

This is because the HTTP response has failed with a 401.

[mindctrl]

This happens when an unauthorized call is made to /api/faust/auth/token, which outputs the error shown in the screenshots above. Reference:

faustjs/packages/faustwp-core/src/server/auth/middleware.ts

Line 36 in 42cbe14

res.end(JSON.stringify({ error: 'Unauthorized' }));

Screenshots:

We have an issue internally for looking at ways to improve this.

[mindctrl]

Noting that on faustjs.org, a 401 can be seen on every page load when logged out.

Related: when logged in on faustjs.org, two requests are made to /api/faust/auth/token. Of course they respond with 200 since I'm logged in, but it's two calls nonetheless.

[josephfusco]

I am currently experiencing the same issue 401 response on every page load made to /api/faust/auth/token.

Note that setting experimentalToolbar: true in faust.config.js will exhibit similar behavior due to the current implementation of the toolbar being client side, however in this case, the 401s happen regardless of experimentalToolbar being absent or explicitly set to false.

Expected behavior without 401s can be observed with the following versions

    "@faustwp/cli": "^1.1.4",
    "@faustwp/core": "^1.1.2",

The 401s were observed after updating to the following canary versions

    "@faustwp/cli": "^0.0.0-20231205203747",
    "@faustwp/core": "^0.0.0-20240109203741",

[josephfusco]

The behavior reported yesterday can be observed using today's release.

package.json

    "@faustwp/cli": "^2.0.0",
    "@faustwp/core": "^2.0.0",

faust.config.js

experimentalToolbar: false

To clarify, the expected behavior when not using the Toolbar is that Faust should not be making authenticated requests on every page load.

Note the 401 issue was not observed in the last version we used; @faustwp/core@1.1.2

[mindctrl]

This is fixed in #1724 and is going out for release within the next few minutes.

[jan-clockworkwp]

I can confirm that on the canary packages:

    "@faustwp/cli": "^0.0.0-20231205203747",
    "@faustwp/core": "^0.0.0-20240129203730",

and with

experimentalToolbar: true,

on localhost setup and with no user logged in accessToken.js file still throws 401 (Unauthorized) console.log error. When experimentalToobar feature is set to false, no error is thrown. Is this expected behaviour? Or there is improvement planned for experimentalToolbar feature? Many thanks!

[jan-clockworkwp]

Probably worth mentioning that there is as well Apollo Client error logged in the console, when experimentalToolbar: true and user is logged in. Basically when the 401 (Unauthorized) is not thrown, then the Apollo one is. According to Apollo error message seems like it can be related to missing ID on queried data. I have tried it with "@apollo/client": "^3.9.2", and "@apollo/client": "^3.6.6", versions.