It turns out that SE chat is a bit more restrictive. For example, this URL:
https://lackadaisical-appeal.glitch.me/hnq/+?filter=tags contains 'number'
does get posted correctly to the chat web server:
but when the server returns the response page, the URL is reduced to:
This is not a visual glitch as on my server as I see calls being done with
tagscontainsnumber, so this is what ended up being stored as URL for the SE chat bot to use.
I've found that I can work around this issue by doing the URL encoding upfront:
which does give me a feed with the applied filter:
I'm not sure why the URL needs to go through this sanitizing step on the chat server, specially if the URL itself doesn't seem to be causing problems or being blocked when using the workaround.
- Add a warning / error message if you enter "illegal" characters in the
- URL Encode the
feedUrlbefore it is posted to the server
- Do not sanitize the URL on the server.
If none of these can or will be implemented, I'll accept an answer that shares the implementation details so that it is less of a surprise what happens.