unable to connect to solr via splainer.io

[dhaivat-dave]

I have been using splainer.io for a while now and its an amazing tool for troubleshooting solr queries.

In past week, when i was trying to connect to one of our solr instances (only accessible via specific ips), the splainer unable to connect. The same link is opening all okay when i try to connect to in new tab in the same browser. Due to security reasons, i can not share the exact url but this setup was working all okay earlier. I have enclosed the screenshot to highlight the issue.

[epugh]

Soo... I suspect it's due to you having an updated browser and it enforcing permissions... The browsers have gotton progressively tougher on what they allow through from a security perspective. Please see this comment: #99 (comment)

We really need to add proper CORS support to Solr... Would you be able to try the splainer Solr package that I linked in the comments?

[dhaivat-dave]

Hi Eric,

thank you for quick response.

I will give it a try with splainer solr plugin, I am using Solr 8.11 I believe, it's compatible with the same?

Also, I am still wondering why it stopped working suddenly. I don't see any errors related to cors in network tab, infact, the request is 200, the issue is that it's not returning any response. The same link is getting resolved in the same browser?

[epugh]

My assumpition on why it quit working is your browser updated and enforced new security. When you do the direct link, you avoid all the security stuff.... So it works just fine... It's because we load Solr response using JSONP, so if you are on http and solr is on hTTPS and vice versa that can cause issues.

As far as packages go, they are kind of new, and they have become more robust in the 9x line. I know the plugin works with the recent 9.4 release of Solr... Not sure on 8.11... Would love to hear how it goes with the package on 8.11!

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please do advocate for this issue and ideally submit a patch to get the attention of the maintainers!