Re: [fossil-users] CORS requests and the JSON API?

2013-02-07 Thread Themba Fletcher
Whoops -- please ignore the previous stuff for now. You have a doubled "Access-Control-Allow-Origin" header in your response: 1. Access-Control-Allow-Headers: x-requested-with 2. Access-Control-Allow-Methods: POST, GET, OPTIONS 3. Access-Control-Allow-Origin: * 4. Access-Con

Re: [fossil-users] CORS requests and the JSON API?

2013-02-07 Thread Themba Fletcher
If I understand correctly the OPTIONS request is forced by the fact that your POST's content-type is application/json -- Any request that's not a Simple Request gets a preflight because the W3C says so. Simple requests are defined as (emphasis mine): >- Only uses GET or POST. If POST is used

[fossil-users] CORS requests and the JSON API?

2013-02-07 Thread Stephan Beal
Hi, all, i am trying, as a proof-of-concept, to host a fossil repo using the new Google Drive feature of being able to host HTML/JS/CSS (as a basis i'm using an existing custom fossil UI built on the JSON API). It's _almost_ working but falls flat due to CORS (cross-origin calls) limitations and i

Re: [fossil-users] translating fossil

2013-02-07 Thread Stephan Beal
On Thu, Feb 7, 2013 at 12:18 PM, Александр Орефков wrote: > For example, "json timeline" not allow me get all kind of events, only > one of chekins, wiki, branch, tickets... > The main reasons for that are because the result format and underlying logic both get more complex if it has to handle mu

Re: [fossil-users] translating fossil

2013-02-07 Thread Александр Орефков
2013/2/7 Stephan Beal : >> >> #ifdef LANG_RU >> ... >> #elif LANG_EN > > > This approach breaks badly if one of us changes printf-style formatting in > the output and you do not modify the RU version. Such changes can cause > anything from garbled output to segfaults, depending on the compiler and

Re: [fossil-users] translating fossil

2013-02-07 Thread Stephan Beal
On Thu, Feb 7, 2013 at 6:25 AM, Александр Орефков wrote: > #ifdef LANG_RU > ... > #elif LANG_EN > This approach breaks badly if one of us changes printf-style formatting in the output and you do not modify the RU version. Such changes can cause anything from garbled output to segfaults, dependin

Re: [fossil-users] casE-senSitive?

2013-02-07 Thread Jan Nijtmans
2013/2/6 Stephan Beal : > Fossil doesn't do any special > interpretation of content other than to complain/warn if a file contains > Windows-style newlines. (The newer UTF-related code has a similar check for > invalid UTF, i believe.) Currently, fossil only gives a warning when it encounters CR/N

Re: [fossil-users] ssh transport and tcsh --off topic

2013-02-07 Thread j. v. d. hoff
On Thu, 07 Feb 2013 00:05:48 +0100, Richard Hipp wrote: On my debian box, /bin/sh is a symlink to /bin/dash (which I have never heard of before). `dash' is the 'debian almquist shell': http://en.wikipedia.org/wiki/Debian_Almquist_shell (and also http://en.wikipedia.org/wiki/Almquist_she