Hello, I just made Fossil aware of 301. Is there any value in having Fossil present the HTTP status to the user when sync/clone operations happen? For example, should the user be notified more than is already done (it outputs the fact that redirect happened):
$ fossil clone http://edwardlblake.com/projects-attic/bitsyhex/index.cgi repo1.fossil redirect to http://www.edwardlblake.com/projects-attic/bitsyhex/index.cgi/xfer Round-trips: 2 Artifacts sent: 0 received: 42 *** time skew *** server is slow by 75.6 seconds Clone finished with 824 bytes sent, 230579 bytes received Rebuilding repository meta-data... 100.0% complete... project-id: 767c30b2e042e113f50563194ad656804ef076d4 server-id: 6e18df16cf880f948ee38e470a4aa08883af57ea admin-user: amb (password is "408047") Or is the ``redirect to...'' sufficient? 301 means that it has moved permanently and that the client should update it's URL, whereas 302 means that it is a temporary redirect and the client should continue to use the original URL. If Fossil should alert the user to type of redirect, how should it be presented? Is it as simply as just putting the code at the beginning of the current notice that is output: 301 redirect to... 302 redirect to... Or something else? Or nothing? Thanks, Andy -- TAI64 timestamp: 400000005495cf75 _______________________________________________ fossil-dev mailing list fossil-dev@lists.fossil-scm.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/fossil-dev
