Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 2.5.0b5
Bug #18721 DSN URLs do not support "@" in database names
Submitted: 2011-08-12 21:00 UTC
From: fgp Assigned: danielc
Status: Closed Package: MDB2 (version 2.5.0b3)
PHP Version: 5.3.6 OS: Linux
Roadmaps: 2.5.0b4    
Subscription  


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 21 - 2 = ?

 
 [2011-08-12 21:00 UTC] fgp (Florian Pflug)
Description: ------------ To prevent parseDSN from getting confused, "@" must be represented as "%40" if it occurs in the username, passwort or database part of a DSN URL. This works correctly for usernames and password, i.e. parseURL() uses rawurldecode() to decode these fields after parsing. It doesn't, however, URL-decode the database name, making it impossible to construct DSN URLs for databases with an "@" in their name. The attached patch fixes the problem by using rawurldecode() to decode the database as well.

Comments

 [2011-08-12 21:03 UTC] fgp (Florian Pflug)
Added patch parseDSN_database_rawurldecode.
 [2011-12-20 06:06 UTC] danielc (Daniel Convissor)
-Status: Open +Status: Closed -Assigned To: +Assigned To: danielc
Fixed in r321265.