[DOCS-9266] Unix domain socket paths must be URL-encoded in connection URIs Created: 02/Nov/16 Updated: 30/Oct/23 Resolved: 28/Nov/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Jeremy Mikola | Assignee: | Allison Reinheimer Moore |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Days since reply: | 7 years, 15 weeks ago | ||||||||||||||||||||||||
| Epic Link: | 3.4: Connection String Revisions | ||||||||||||||||||||||||
| Story Points: | 0.5 | ||||||||||||||||||||||||
| Description |
|
The example for UNIX Domain Socket in the connection string docs does not mention that socket paths should be URL-encoded (see: connection string spec). By this point, all drivers that support sockets should handle URL decoding, but it wouldn't hurt to confirm. If anything, it's more likely for non-encoded paths to cause problems (see: |