as the json structure stored is not specific to any database management
system.

to prevent clashing of underscores in client names and underscores used by LIKE.

* Introduced in 5f2e50a0
* Caused the POST payload to be always ignored, breaking the function completely.
* Great job finding and debugging this, Honza Žerdík.

Shuffle directories and filenames to get rid of historic cruft and to better reflect contrib/production status

Radko Krkoš authored 6 years ago and Pavel Kácha committed 6 years ago

* The warn() variant was never documented and was deprecated in Py3.3.
* Correct variant warning() worked in all Python versions since logging
  module inclusion.

Details: https://bugs.python.org/issue13235



Signed-off-by: Pavel Kácha <ph@cesnet.cz>

Radko Krkoš authored 6 years ago and Pavel Kácha committed 6 years ago

* WSGI specification is loosely defined, some servers (nginx, wsgi_ref, ...)
  would hang if no payload was present and CONTENT-LENGTH was missing.
* We now implement the correct (more strict) behaviour on application part
  according to specification.

Signed-off-by: Pavel Kácha <ph@cesnet.cz>

Radko Krkoš authored 6 years ago and Pavel Kácha committed 6 years ago

Signed-off-by: Pavel Kácha <ph@cesnet.cz>

Radko Krkoš authored 6 years ago and Pavel Kácha committed 6 years ago

* No longer silently accept pattern 'a@b@c', otherwise stay compatibile.
* Valid patterns are: 'user@fqdn', '<user@fqdn>', 'user <user@fqdn>',
  'user surname <user@fqdn>', no Unicode support, multiple e-mails
  separated by comma are allowed.
* Replace email.utils.parseaddr() with extended regular expression.
* Remove import email.utils as no other users exist.

Signed-off-by: Pavel Kácha <ph@cesnet.cz>

Radko Krkoš authored 6 years ago and Pavel Kácha committed 6 years ago

Signed-off-by: Pavel Kácha <ph@cesnet.cz>

* All input files (config, maps, idea schema) are expected in UTF-8,
* Add helper get_method_params() hiding 2vs3 internal differences,
* Report Python version in getInfo,
* Argparse compatibility fixes.

Cert checking now works correctly in both "SSLVerifyClient required" and "SSLVerifyClient optional" (authenticators do safety check themselves)