@kabilar the queryservice is setup in AWS EC2, separate instance. And As I showed you over the call, the https has been enabled for queryservice.

@aaronkanzer do you have any suggestions?

The request header from network tab, when making request.

Sequence diagram for the above request, where we're facing https issue.

Update: With a latest update to queryservice, I no longer see HTTPS issue as before. Rather a CORS issue.

Hi @tekrajchhetri, after discussion with @aaronkanzer, perhaps the assertions and evidence endpoints are not available for the queryservice (API docs) and this is why the 404 is returned. Is this evidence endpoint live?

Additionally, perhaps these GET requests needs to be against queryservice.brainkb.org instead of beta.brainkb.org:

• GET https://beta.brainkb.org/assertions?_rsc=ua88w 404 (Not Found)
• GET https://beta.brainkb.org/evidence?_rsc=ua88w 404 (Not Found)

Thanks.

@kabilar

Please find find my answers below.

• after discussion with @aaronkanzer, perhaps the assertions and evidence endpoints are not available for the queryservice (API docs) and this is why the 404 is returned. Is this [evidence endpoint] (https://github.com/sensein/BrainKB/blob/f29c1536b6e1314fa8ac136dea01862fb5eae457/WebApp/Web/views.py#L217) live?
  Additionally, perhaps these GET requests needs to be against queryservice.brainkb.org instead of beta.brainkb.org:
  GET https://beta.brainkb.org/assertions?_rsc=ua88w 404 (Not Found)
  GET https://beta.brainkb.org/evidence?_rsc=ua88w 404 (Not Found)

--> Yes, there will be assertion/evidence endpoint. But the error that you're seeing is not because we don't have assertion/evidence endpoint. It's because nothing has been implemented for assertions/evidence menu as of now. We will possibly start next week or so once we fix some issues with our model.

But the error that you're seeing is not because we don't have assertion/evidence endpoint. It's because nothing has been implemented for assertions/evidence menu as of now.

@tekrajchhetri Sorry, I am not exactly sure what you mean.

@kabilar we could discuss in our meeting today.

@kabilar closing this issue as I've resolved the issue.

Thanks @tekrajchhetri. Thats great. I will review the pull request.

Just as a heads up. Its typical practice to keep the issue open until the pull request has been merged, tested, and the changes are GA.

@kabilar Thanks for that info, I am opening it. We can close it after we merge the pull-request.