I realize that you probably understand this problem far better than I
do, so I apologize again for being dense, but the below not does appear
to me to *precisely* describe my problem. Looking back, my explanation
is not as clear as it could be. I appreciate you trying to help, and I
will try to express myself better.
> I understood that from inside your network, you can access your
> repository that is inside your network, and access the official
> Subversion repository which is outside your network, but from outside
> your network you cannot access your own repository which is inside
> your network.
To clarify one point, "from home" means using my router's IP address
instead of "localhost" or the machine's IP. I was told by the router's
tech support that this is the same as if I was accessing it from outside
my network. How accurate that is, I don't know, but it's all I have to
go on. If I turn off port 81 forwarding on the router, both the browser
and "svn ls" to fail, if that's any indication.
From home: access to my home repo works.
access to the Subversion repo works.
From work: access to my home repo does not work.
access to the Subversion repo works.
> Thus, my only guess is that you have some kind of proxy
> or other similar type of software restricting (perhaps
> unintentionally) the types of HTTP methods allowed on incoming, but
> not outgoing, traffic.
That appears to imply one or more of the following:
- The svn.exe client is using HTTP methods to my home repo that are
different than the ones it uses to the Subversion repo, and my work
proxy is blocking the former but not the latter.
- My home repo is using HTTP methods to send back information that are
different than the ones used by the Subversion repo, and my work proxy
is blocking the former but not the latter.
- My home repo (or router, or some other piece) is blocking the HTTP
methods that it receives from my work, but not the ones that it receives
from the (same version of) the svn client that is used inside my home
network.
If I've missed some, please let me know.
> Not applicable: serf and neon are client-side, not server-side,
> libraries. Type "svn --version" to discover which of these libraries
> is available in your client.
Then I won't be able to switch them out until I upgrade the client to
1.5. I'll give that a shot and see what happens. I wasn't *quite*
prepared to do that here at work, but if I'm careful about what features
I use, I guess it won't hurt anything.
> HTTPS of course trades speed for security, and HTTP is already slower
> than SVN-protocol access. So you'll have to evaluate whether the
> speed hit of HTTPS is acceptable.
I don't think that will be an issue. I expect the number of users to be
small, 10 or less, and access to be occasiona, weekly, at its most
frequent.
Thanks,
Brad
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-08-22 20:47:24 CEST