Also, could you open the Developer Tools and go to the Network tab? The request causing the problem should show up there. Copying the request and response (if there is one) could be helpful.
If you are using the security solution it might also be helpful to check the roles associated with your user (whether there are any differences to your team mates)
The only request that isn't a 200 or 304 is this one (it doesn't have a http status code): /_search?rest_total_hits_as_int=true&ignore_unavailable=true&ignore_throttled=true&preference=1591192933292&timeout=30000ms
This request looks like like a Courier request. It's interesting this is only happening in firefox - could you check whether the same request is there in Chrome as well and whether there are any differences in parameters/payload?
The triggering url looks like http://logs.something/app/kibana#/discover?_g=()&_a=(columns:!(_source),index:cc79f970-d2ff-11e9-b2c6-dbd2f4f2af8b,interval:auto,query:(language:lucene,query:''),sort:!(!('@timestamp',desc)))
Update: the index pattern that I was working on had both the words "ad" and "google" in there, and that had the adblocker kick in, which just so happened to be installed on both browsers
Deactivating the adblocker solved the issue.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.