On Wed, Feb 11, 2015 at 11:18 AM, Joerg Sonnenberger <
jo...@britannica.bec.de> wrote:
> On Tue, Feb 10, 2015 at 06:38:02PM -0800, bch wrote:
> > For the record, what Mr Beal is talking about is called a "scheme
> > relative URI" -- which I know about since an HTTP parser I work with
> > handles t
On Tue, Feb 10, 2015 at 06:38:02PM -0800, bch wrote:
> For the record, what Mr Beal is talking about is called a "scheme
> relative URI" -- which I know about since an HTTP parser I work with
> handles them so poorly. However, if your browser works w/ (eg)
> Wikipedia, you are already using scheme-
Richard Hipp writes:
> Good point. But you don't need a separate script. Just add a line to
> the existing Fossil CGI script:
>
> setenv: HTTPS on
>
> Let us know if that helps.
Thanks a lot. That helps!!
It looks it does not automagically since my Hiawatha web server is
behind reverse-p
For the record, what Mr Beal is talking about is called a "scheme
relative URI" -- which I know about since an HTTP parser I work with
handles them so poorly. However, if your browser works w/ (eg)
Wikipedia, you are already using scheme-relative URIs.
-bch
On 2/10/15, Richard Hipp wrote:
> On
On 2/10/15, Francis Daly wrote:
> >
> I suspect that fossil Just Works if the cgi-server puts "HTTPS=on"
> into the environment; and I guess that your web server does not do that.
>
> Can you run a separate cgi script with content like
>
Good point. But you don't need a separate script. Just ad
On Tue, Feb 10, 2015 at 10:50:24PM +0100, Gour wrote:
> Francis Daly writes:
Hi there,
> > So presumably all that is needed is to use the fossil-cgi equivalent
> > to fossil-http's "--https" argument.
>
> My site is set to use https-only, so to me it seems it's still the
> original question how
Francis Daly writes:
> It looks like it is the
>
>
> entry on the page. (https://fossil.atmarama.net/repo.cgi/index)
Right.
> So presumably all that is needed is to use the fossil-cgi equivalent
> to fossil-http's "--https" argument.
My site is set to use https-only, so to me it seems it's
Stephan Beal writes:
> This sounds like some of the generated links are incorrectly hard-coded to
> http. It "should" be okay for fossil to use links with start with // (with
> no "scheme:" part), which is the conventional way of saying "use the
> current scheme, namely http resp. https.
This so
On Tue, Feb 10, 2015 at 05:15:39PM +0100, Stephan Beal wrote:
> On Tue, Feb 10, 2015 at 5:12 PM, Gour wrote:
Hi there,
> > When I visit Fossil site via https I see everything is fine, so I wonder
> > what do I miss?
> If you can tell us which links are still being generated with "http://";
> th
On Tue, Feb 10, 2015 at 5:12 PM, Gour wrote:
> When I visit Fossil site via https I see everything is fine, so I wonder
> what do I miss?
>
This sounds like some of the generated links are incorrectly hard-coded to
http. It "should" be okay for fossil to use links with start with // (with
no "sc
Hello,
I did resolve my issue with HTTPS and now I can login to the admin site,
sync repo with my desktop, but Firefox/Chromium browsers are complaining
when I visit site (HTTPS-only) about 'Insecure content' - some
unencrypted elements on this website has been blocked. If I temporarily
disable pr
11 matches
Mail list logo
