openlp-core team mailing list archive

[mahfiaz <mahfiaz@xxxxxxxxx>]

It turned out that urlparse uses & and ; as equivalent separators.

urlparse.parse_qsl('data={"request":"da;ta=some"}')
returns
[('data', '{"request":"da'), ('ta', 'some"}')]

urllib.urlencode([('data', '{"request":"da;ta=some"}')])
returns
'data=%7B%22request%22%3A%22da%3Bta%3Dsome%22%7D'

Although we could replace these strings in httpserver.py in ready_read()
right before passing the string to urlparse.parse_qs(), it seems like a
wrong place to fix it.

-- 
You received this bug notification because you are a member of OpenLP
Core, which is subscribed to OpenLP.
https://bugs.launchpad.net/bugs/908226

Title:
  Traceback when sending # or ; character from remote search or alert
  field

Status in OpenLP - Worship Presentation Software:
  Fix Committed

Bug description:
  This is a regression compared to 1.9.7
  Maybe there are more characters which need special treatment besides # and ;

To manage notifications about this bug go to:
https://bugs.launchpad.net/openlp/+bug/908226/+subscriptions