| Summary: | URIish accepts incorrect URIs | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Technology] JGit | Reporter: | Dmitry Neverov <dmitry.neverov> | ||||
| Component: | JGit | Assignee: | Christian Halstrick <christian.halstrick> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | matthias.sohn, stefan.lay | ||||
| Version: | unspecified | ||||||
| Target Milestone: | 1.0.0 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Dmitry Neverov
Created attachment 170944 [details]
test to reproduce the problem
I try to fix this with http://egit.eclipse.org/r/#change,1690. I solved one thing differently. I cannot come up with a URISyntaxException because the syntax is not so bad as we both think. URI's are mainly a scheme, a colon and then a scheme specific part (which can be nearly anything). Not the generic URIish parsing but the ssh specific code can tell that the URI is wrong. So, in my proposal the URI parsing will go through but calling the various "...canHandle()" methods in our transport framework will fail. merged as 2160c09dd4f678c5f2f8e730945be637210b39de |