search: when using operators, putting the value in quotation marks breaks search and returns 502

[aliceisjustplaying]

If I search for from:alice.bsky.sh, everything's fine.

If I search for from:"alice.bsky.sh", after whatever timeout is set, I get this instead:

URL: https://oyster.us-east.host.bsky.network/xrpc/app.bsky.feed.searchPosts?q=from%3A%22alice.bsky.sh%22&limit=25&sort=top

This happens with things like lang:en vs lang:"en" too (which is how I discovered it the first place, searching for lang:en-au because some posts are tagged with it, and couldn't find anything.

[goeo-]

somehow can't reproduce this at all from my pds, or by skipping the pds proxying and talking to api.bsky.app directly - very confused

[moll-dev]

Can reproduce 🤷🏼 (firefox if that helps)

[clement-cln]

Can reproduce on the Bluesky iPhone app:
Build version: 1.91.1.464; Bundle info: 49ab4867a (prod); Bundle date: 24091901; Platform: ios

[brianolson]

yeah

fine:
https://bsky.app/search?q=from%3Aalice.bsky.sh

nope:
https://bsky.app/search?q=from%3A%22alice.bsky.sh%22

but worth noting also nope:
https://bsky.app/search?q=from%3Aalice.bksy.sh

so if I typo the search term in such a way that I would just get nothing, it also has the same 500-like error

[goeo-]

here is what that looks like for me

[bnewbold]

Does seem like a bug, and not arguing validity, but out of curiosity/prioritization: how did you encounter this? I don't think any of our search filters support free-form text, so I can't think of a use-case for putting quotes around just the facet value.

I think if you put quotes around the prefix and the value, it gets treated as a token, not parsed as a filter (which is intuitive to me, at least).

[aliceisjustplaying]

i was searching for lang:en-au to find the sole user tweeting with that language code and when they didn't turn up anything, on a whim i tried lang:"en-au". that's it.

[aliceisjustplaying]

idk. old google reflexes.