Last modified: 2013-10-21 23:40:02 UTC
The Visual Editor is writting problems to that url, but does not use https, so that is a unsafe operation, which should be avoid, because it is a secure hole. This should be a blocker for the coming roll out. Thanks.
No data goes over the wire that is personally-identifying, so I would disagree that this is a blocker; however, yes, this is good practice and we should try to do thing (especially, to avoid unexpected mix-mode for users).
Note that the server will no longer be receiving these feedback items, so the original demand has less need.
Yuvi set up https proxying: https://parsoid.wmflabs.org/
