On Jan 30, 2010, at 12:33 PM, <[email protected]>
<[email protected]> wrote:
> Hello again
>
> Here are some more informations about my configuration:
>
> * Server OS: Windows Home Server(Windows 2003 based)
> * running two different fossil repositories on ports 8000 and
> 8001(Fossil version [a3c97c9063] 2010-01-21 20:53:59)
> * client OS: XP prof.
> * Browser: Firefox 2
>
> If i switch between the repositories, the current login becomes
> invalid.
>
> I opened the cookie-dialog of firefox. There i can see One cookie from
> my server, named
> fossil_login_
I guess firefox 2 sends to same cookie to port 8001 as it sends to
port 8000. as if localhost:8000 and localhost:8001 were the same
website.
If you switch to running a webserver (on port 80, say) and run your
repositories as CGI scripts, the names of each CGI script will be
appended (as hex) to the login cookie name and this problem will go
away. It is not clear to me what (if anything) we ought do to Fossil
to make it easier to work around this.
There was another recent request for the ability to serve multiple
repositories off of the same TCP port without using a web server. The
current syntax to launch a stand-alone server is:
fossil server REPOSITORYFILE
Suppose we expanded this to allow multiple repositories to be named on
the command-line. So if you had a directory full of repositories, you
could do:
fossil server *.fossil
Suppose the names of the repositories files are abc.fossil,
def.fossil, ghi.fossil and so forth. Then to reach each repository,
visit:
http://localhost/abc
http://localhost/def
http://localhost/ghi
And so forth. If this functionality were implemented, then the cookie
names would be fossil_login_2F616263, fossil_login_2F646566, and
fossil_login_2F676869. Since the cookie names are different, you
could log onto all repositories all at once. If no repository is
specified in the URL (if you enter http://localhost/) what should it
do? Show an error? Return a list of repositories? Choose the first
one named?
Perhaps the syntax should be:
fossil server --directory FOLDER_HOLDING_REPOSITORIES
In that case, fossil is able to serve any fossil repository in the
named directory. The particular repository chosen by the path in the
URL. With this syntax, new repositories can be added to the site
without having to restart the server - simply move files into the
appropriate folder. We still have the problem of what to do with an
unknown path.
>
> I think the problem is, that there is no 'repository-extension' behind
> the last underscore.
>
> The test_env-information, given by one of the servers is:
> g.zBaseURL = http://<DELETED BY ME>:8000
> g.zTop =
> GATEWAY_INTERFACE = CGI/1.0
> HTTP_COOKIE =
> fossil_login_=1%2F5A300CEC00A1528DAE8F21FD975FE6742534E95E2D2443872E
> HTTP_HOST = <DELETED BY ME>:8000
> HTTP_USER_AGENT = Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
> rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14 (.NET CLR 3.5.30729)
> PATH_INFO = /test_env
> QUERY_STRING =
> REMOTE_ADDR = <DELETED BY ME>
> REQUEST_METHOD = GET
> REQUEST_URI = /test_env
> fossil_login_ = <DELETED BY ME>
>
> Maybe this information helps. Feel free to contact me, if you need
> further information.
>
> Wolfgang
>
>
> _______________________________________________
> fossil-users mailing list
> [email protected]
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
D. Richard Hipp
[email protected]
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
