[DRIVERS-808] Specify behavior of empty authSource URI option Created: 30/Jan/20 Updated: 05/Aug/21 |
|
| Status: | Implementing |
| Project: | Drivers |
| Component/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | John Stewart (Inactive) | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Driver Compliance: |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
As far as I can tell there is no language in the URI spec defining how a present but empty authSource in the URI should be handled, nor does there appear to be a test for this situation. Can this case be explicitly specified? It may be convenient for users to treat an empty authSource the same way as if authSource was not provided at all. This is also in line with common web development conventions. |