After a lot of hair-pulling, the problem was solved. The issue is, as is usual for me, the Great Firewall. I have a back door to get around it, but that back door's pipeline is a bit narrow so I don't use it for all web sites. Instead I use a PAC file to decide if a given URL is going to take me through my back door or through a direct link.
The approach I used in the PAC file is "if this URL matches any of the following patterns, go through the proxy, otherwise go direct". One of my rules happened to match the login URL for my repositories. When I was logging in I was coming in through the proxy, but when I was trying to access the repository otherwise I was coming in directly. Confusion ensues. The solution was, once the problem was identified, trivial: add a snippet of logic at the head: "if this URL matches any of the following patterns, go direct". This allows me to insert sites that I know for certain work to avoid the possibility of accidentally catching up on a proxied URL pattern. On 12 October 2011 20:40, Michael Richter <ttmrich...@gmail.com> wrote: > On 12 October 2011 19:01, Richard Hipp <d...@sqlite.org> wrote: > >> On Wed, Oct 12, 2011 at 12:20 AM, Michael Richter >> <ttmrich...@gmail.com>wrote: >> >>> Using a recent version of fossil (Fossil version 1.19 [6092935ff2] >>> 2011-10-05 02:03:04) I can't log in to any repository at all (including >>> repos I've had up for over a year without a problem) except on the local >>> machine. I've attached an example of this behaviour as an empty repository. >>> There are two users on this repo: michael and nii. The former is >>> Super-user and the latter is Developer. Both have the password 12345. I >>> can only log in as "michael" when run locally (and, indeed, hitting Logout >>> leads me to an "Unable to connect" message). When running remotely I can >>> access the Login page, but can't actually log in. It *says* I've been >>> logged in, but going anywhere other than the login window says I'm not >>> logged in. >> >> >> There were some (backwards compatible) security enhancements to login >> about a year ago. But nothing has changed lately. What changed on your end >> to make it stop working? >> > > Well, that's the thing. I haven't had cause to use Fossil remotely in a > long time, so I'm not sure what changes happened nor when they did. I'm > sniffing the network right now to see what's happening. > > >> Login uses cookies. Did you turn off cookies in your browser? >> > > Nope. Cookies work fine (except for the ones I've explicitly > black-listed). > > >> The login cookie contains (among other things) the first 16 bits of your >> IP address. Did you switch to IPv6 all of a sudden? Are you on a >> multiplexed connection where the IP address changes with each packet? >> > > That, sadly, is a decided possibility. I'm behind the Great Firewall and > use some tricksy proxy stuff to get around it. I'll investigate this angle > more closely. It could be that something is triggering a switch through the > proxy for some transactions only. > > -- > "Perhaps people don't believe this, but throughout all of the discussions > of entering China our focus has really been what's best for the Chinese > people. It's not been about our revenue or profit or whatnot." > --Sergey Brin, demonstrating the emptiness of the "don't be evil" mantra. > -- "Perhaps people don't believe this, but throughout all of the discussions of entering China our focus has really been what's best for the Chinese people. It's not been about our revenue or profit or whatnot." --Sergey Brin, demonstrating the emptiness of the "don't be evil" mantra.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
