-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
most, or all, searches of room content fail (with CORS-related errors) #5517
Comments
Comparative test resultsAndroid 6.0.1, Riot.im 0.7.03 (G-da8a7535b)
Three of three searches succeeded. https://riot.im/develop/ in SeaMonkey 2.49.1
– so there's some parallel with an adjacent bug report by me, although I can't tell whether it's coincidence or a direct relationship between the two: This apparent redirect is novel, I'll test in a third browser to tell whether anything like it can be reproduced. (Too soon to raise a separate issue, or change the title of this one …) |
Briefly:
Comparative test resultsChromium
|
Chromium
– 2017-11-05 ~14:55 |
The search that failed at #5517 (comment) above now succeeds,and the results appeared reasonably quickly. Re: #5666 (comment) as we have closure there, so I'm closing here. |
I see leak-oriented #5373 and #5374 and more recent #4541 … I find a more general problem; searches no longer succeed.
(I can't recall when I last had a search result.)
The text was updated successfully, but these errors were encountered: