On Mon, Mar 21, 2011 at 3:21 PM, Richard Hipp <d...@sqlite.org> wrote:
> > > On Mon, Mar 21, 2011 at 10:01 AM, Michael Richter <ttmrich...@gmail.com>wrote: > >> OK, perhaps I'm being as thick as a whale omlette here, but I cannot get >> this to work at all. >> >> First attempt: "relay-to" was set to www.fossil-scm.org:80, "listen" was >> set to 8180. I access http://localhost:8180 and I get ... the SQLite >> home page, not Fossil's. Tinkering around with various values for >> "relay-to" always gets me either SQLite's home page or error messages. >> >> What, precisely, should I be setting up in there? >> > > Bummer. > > www.sqlite.org and www.fossil-scm.org use the same IP address. The web > server distinguishes between them by looking at the HOST: parameter in the > HTTP header. But with the setup above, the HOST: parameter is being set to > "localhost:8180" which the web server then defaults to SQLite. > > I'm not sure how to work around that. Anybody else have any ideas on how > to eavesdrop on the TCP/IP connection between the web browser and the Fossil > web server? > > > >> >> >> On 21 March 2011 21:49, Michael Richter <ttmrich...@gmail.com> wrote: >> >>> Oops. I didn't see this, Richard. Sorry. I'll get this set up now and >>> send you the results. >>> >>> Once I figure out how to get Tcl working. :) >>> >>> >>> On 17 March 2011 01:21, Richard Hipp <d...@sqlite.org> wrote: >>> >>>> On Wed, Mar 16, 2011 at 11:30 AM, Michael Richter <ttmrich...@gmail.com >>>> > wrote: >>>> >>>>> >>>>> OK, this is the sequence I've tried on my main workstation (Ubuntu >>>>> 10.04): >>>>> >>>>> 1. Delete all fossil-scm.org cookies. >>>>> 2. Close my browser (Chrome 10.0.648.134). >>>>> 3. Re-open my browser. >>>>> 4. Go to fossil-scm.org. >>>>> 5. Log in. >>>>> 6. Click on Timeline. >>>>> >>>>> Result: "you are not logged in". >>>>> >>>>> If I repeat this experiment on my backup machine (Windows XP, >>>>> Chrome 10.0.648.133) I do not have this problem. Curious about that, I >>>>> tried other browsers (Opera, Firefox) on my main machine again. Again I >>>>> don't have this problem. >>>>> >>>>> The issue seems specific to Chrome under Linux in my case. I have no >>>>> idea how to proceed from here on however because I can't figure out what >>>>> could be going wrong that affects only Fossil and nothing else, especially >>>>> since I killed all cookies related to the fossil-scm.org domain. >>>>> >>>>> Any suggestions or ideas on what's next to investigate? >>>>> >>>> >>>> The attachment is a Tcl/Tk script that sets up a TCP/IP proxy. Please >>>> make it point to http://www.fossil-scm.org/ and then point your Chrome >>>> browser at the proxy. Record your traffic. Send me what you see. >>>> >>>> >>>> -- >>>> D. Richard Hipp >>>> d...@sqlite.org >>>> >>> >>> >>> >>> -- >>> "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. >> > > > > -- > D. Richard Hipp > d...@sqlite.org > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > Use a packet level sniffer like WireShark (http://www.*wireshark*.org) Mark
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
