Issue #834 – snarfed/bridgy – entirely possible, I will investigate
entirely possible, I will investigate in https://dougbeal.com/2018/07/20/pfefferle-wordpress-webmention-ensure-unicode-coverage-in-tests/
6 responses on “Issue #834 – snarfed/bridgy – entirely possible, I will investigate”
Leave a Reply
You must be logged in to post a comment.
post:
https://dougbeal.com/2018/07/16/snarfed-bridgy-fed-bridgy-error-on-like-%c2%b7-issue-28-%c2%b7-snarfed-bridgy-fed/
nows it looking like an encoding issue –
`on-like-xb7-issue-28` vs `on-like-%c2%b7-issue-28`
whee, Unicode!
that 400 error is from your web server (looks like WordPress?). the url with the `x`es is a logging artifact, purely internal to bridgy. i think it’s correctly sending the %-encoded url as the webmention target (search that error json for “target.”)
similar: #625
@dougbeal friendly ping. is the WordPress webmention plugin maybe not handling Unicode in URLs correctly?
tentatively closing. (bridgy has successfully sent webmentions to many other urls with unicode chars before in the past.) @dougbeal feel free to reopen if you do determine this is still a bridgy bug somewhere!