|
3 |
edited tags
|
||
|
|
||||
|
2 | added 201 characters in body; added 11 characters in body | ||
|
When I point the importer at a URL like
I'm testing on our private repositories, which use Windows authentication over HTTPS; unfortunately, this makes it very difficult to get at them with other tools sometimes. I am also not real sure how the SVN auth occurs, because it seems like a working client connection hits a 401 first before sending the "real" security token. Another fun fact: our SSL cert is not properly trusted, so it's possible that the svnsync would need Anyway, I have access to the server so I can grab the raw files and host them elsewhere. It would be cool if the https access just worked, though. Edit: With 1.0.38, it now appears to get further and then stalls at "Initializing Conversion". I launched with logging, and I'm letting it sit there, but it doesn't seem to be dumping any log file yet. |
||||
|
1 |
|
||
Subversion import from NTLM-secured HTTPS repository failsWhen I point the importer at a URL like
I'm testing on our private repositories, which use Windows authentication over HTTPS; unfortunately, this makes it very difficult to get at them with other tools sometimes. I am also not real sure how the SVN auth occurs, because it seems like a working client connection hits a 401 first before sending the "real" security token. Another fun fact: our SSL cert is not properly trusted, so it's possible that the svnsync would need Anyway, I have access to the server so I can grab the raw files and host them elsewhere. It would be cool if the https access just worked, though.
|
||||