Authenticated fetch not allowed

[AronBuzogany]

This PR Fixes #71 by doing the following:

• Try to fetch the resource unauthenticated.
• If it fails, or returns status code 401 or 403 AND user is logged in, try it authenticated

[pheyvaer]

This is what the authentication library already does. In other words, this code adds something that is already done.

[AronBuzogany]

This is what the authentication library already does. In other words, this code adds something that is already done.

This did resolve it though, the Web application now no longer calls an error on the test query when logged in

[pheyvaer]

This is what the authentication library already does. In other words, this code adds something that is already done.

This did resolve it though, the Web application now no longer calls an error on the test query when logged in

That might be the case, but in general it's not a good practice to change your code to fix an issue in another library or server. It could be a temporary fix, but in this case we don't have a full understanding of where the issue is coming from. In other words, which component is causing it?

Regarding the CORS headers, Comunica offers to option to pass a proxy. It would suggest trying this and adding this to the config file. You can use this proxy for testing: https://proxy.linkeddatafragments.org/

[AronBuzogany]

That might be the case, but in general it's not a good practice to change your code to fix an issue in another library or server.

I understand, I thought you meant that Comunica already does exactly what I do.

[pheyvaer]

That might be the case, but in general it's not a good practice to change your code to fix an issue in another library or server.

I understand, I thought you meant that Comunica already does exactly what I do.

No, the authentication library does that. Comunica just uses the fetch.