Ticket #2242 (closed bug: invalid)

Opened 2 months ago

Last modified 4 weeks ago

Percent encode all fields in formdata-based REST transactions

Reported by: lucas Owned by: lucas
Priority: release Milestone: milestone:
Component: shotwell Keywords: publish, publishing, http, percent, encode, encoding, percent-encode, percent-encoding, rest, transaction
Cc: adam@yorba.org, jim@yorba.org, lucas@yorba.org, allison@yorba.org, vera@yorba.org, patrick@yorba.org

Description


Change History

Changed 2 months ago by DefaultCC Plugin

  • cc adam@yorba.org, jim@yorba.org, lucas@yorba.org, allison@yorba.org, vera@yorba.org, patrick@yorba.org added

Changed 6 weeks ago by adam

  • priority changed from high to release

Changed 4 weeks ago by lucas

  • keywords transaction added; transation removed

Changed 4 weeks ago by lucas

  • status changed from new to closed
  • resolution set to invalid

Shotwell already percent-encodes everything that needs to be encoded. Email correspondence with the original bug reporter seemed to imply that he was using non-ASCII characters in his password and so we assumed that we had an encoding problem. We now know, however, that this assumption was incorrect -- Google doesn't even allow non-ASCII characters in passwords. Marking as invalid.

Note: See TracTickets for help on using tickets.