[fossil-users] Command line option for HTTP Auth?

2014-01-28 Thread Andy Bradford
Hello, I've just started a branch for exploring a different way to enable the use of HTTP Authorization headers in requests: http://www.fossil-scm.org/index.html/info/e747041a72 Of course, removing the special character as a flag to enable HTTP Auth could potentially break some users who r

Re: [fossil-users] fossil clone / sync / update with Basic Authentication

2014-01-28 Thread Kees Nuyt
[Default] On Tue, 28 Jan 2014 14:46:29 -0700, Tal Yardeni wrote: >I saw some threads on this topic from 2011, but wanted to see if there was >any change or decision since then. > >I have fossil repos hosted on an Apache server with REMOTE_USER enabled. If >I attempt to clone via the following com

Re: [fossil-users] fossil clone / sync / update with Basic Authentication

2014-01-28 Thread Andy Bradford
Thus said Tal Yardeni on Tue, 28 Jan 2014 14:46:29 -0700: > password for username: > fossil: server says: 401 Authorization Required It seems that Basic HTTP Authorization is somewhat of a hidden feature. When it prompts you for your password, you must prepend # to the password to signal

Re: [fossil-users] fossil clone / sync / update with Basic Authentication

2014-01-28 Thread Stephan Beal
On Tue, Jan 28, 2014 at 11:28 PM, Tal Yardeni wrote: > Are your repos using the Apache server's authentication or the internal > fossil authentication? > Ah, of course. i'm using Fossil's authentication, which (IIRC) uses REMOTE_USER via http://name:password@... > We have no issue authenticati

Re: [fossil-users] fossil clone / sync / update with Basic Authentication

2014-01-28 Thread Tal Yardeni
Stephan, that is great - I don't think the https/SSL piece is the issue since the browser is returning the 401 status code as part of the authentication handshake. In case it matters (and I should have included this info in the initial post) we were using the following fossil version: fossil vers

Re: [fossil-users] fossil clone / sync / update with Basic Authentication

2014-01-28 Thread Stephan Beal
On Tue, Jan 28, 2014 at 10:46 PM, Tal Yardeni wrote: > fossil clone https://usern...@fossil.example.tld/repo/test.fossil > test.fossil > FWIW, all my repos are hosted/cloned this way, but over http, not https, without problem. i unfortunately can't say anything helpful about the ssl support, tho

[fossil-users] fossil clone / sync / update with Basic Authentication

2014-01-28 Thread Tal Yardeni
I saw some threads on this topic from 2011, but wanted to see if there was any change or decision since then. I have fossil repos hosted on an Apache server with REMOTE_USER enabled. If I attempt to clone via the following commands: fossil clone https://usern...@fossil.example.tld/repo/test.fossi

Re: [fossil-users] fossil ui/serv

2014-01-28 Thread Jan Nijtmans
2014-01-28 Mark Janssen : > I have seen something similar in the past, could it be a permissions issue > on the repo or the containing directory? If it's a security issue, this commit could be the coolpit: I cannot explain how, maybe th

Re: [fossil-users] fossil ui/serv

2014-01-28 Thread Mark Janssen
On Tue, Jan 28, 2014 at 12:46 AM, James Turner wrote: > > > I dunno either. Everything is fine on my main development machine. I'll > chalk it up to a messed up virtual machine I guess. Sorry for the > noise. > > I have seen something similar in the past, could it be a permissions issue on the rep

Re: [fossil-users] Fossil 1.28 and SQLite 3.8.0.2

2014-01-28 Thread Jan Nijtmans
2014-01-28 James Turner>: > Thanks for the clarification guys. I'm thinking it's probably safe then > to use 1.28 with our 3.8.0.2 version of SQLite. > > I'll get our in-tree version of SQLite upgraded to the latest after the > unlock. Thanks for your feedback. It is highly appreciated! Regards,