https://bugzilla.wikimedia.org/show_bug.cgi?id=21296

T. Gries <m...@tgries.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #3 from T. Gries <m...@tgries.de> 2011-05-16 10:37:10 UTC ---
At the moment, there are two issues which are causing the problem.

First, the character encoding.

I checked the response headers. The server sends your OpenID identity page
http://certifi.ca/andreasb%C3%BCrki without any character set encoding
information. 

Date: Mon, 16 May 2011 10:20:40 GMT
Server: Apache/2.2.4 (Ubuntu) PHP/5.2.3-1ubuntu6.5 mod_ssl/2.2.4 OpenSSL/0.9.8e
X-Powered-By: PHP/5.2.3-1ubuntu6.5
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
X-XRDS-Location: https://certifi.ca/?xrds=andreasbürki
Content-Length: 314
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Type: text/html

200 OK

I will check the OpenID extension whether it can correctly handle non-ASCII,
ISO-8859-x, and UTF-8 encodings of OpenID uris and X

Secondly, at least today, the certificate is not valid:

"certifi.ca verwendet ein ungültiges Sicherheitszertifikat.
Das Zertifikat ist am 23.02.2011 16:52 abgelaufen. Die aktuelle Zeit ist
16.05.2011 12:24." (Fehlercode: sec_error_expired_certificate)"

The OpenID extension currently ignores log ins with invalid or expired
certificates; it is currently not configurable to "trust" also untrusted
(self-issued), invalid or expired certificates. However, we could think of an
debug option which allows this for test purposes.

-- 
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to