Hi all,

It seems that access using 'https' is breaking our CGI (which itself is written in Ciao). Perhaps some browsers are forcing a HTTPs connection even if HTTP is stated. We will fix this issue as soon as possible.��

Meanwhile there are some alternatives:

��- Try the latest version at github: https://github.com/ciao-lang/ciao
�� ��Be aware that it corresponds to version 1.16.0-alpha.3. There has not been a public announcement yet but beta-testers are welcome to try it and report bugs!��

��- Use 'http' (or a browser that do not enforce https)

��- Use the URLs to files (which are hidden as 'url=' parameters in the download.cgi), e.g.:


Bests,

On Thu, Mar 23, 2017 at 5:35 AM, GreyHat LispHacker <greyhatlisphacker@gmail.com> wrote:
I just attempted again and cannot reproduce the error.�� It appears to work on both Windows and FreeBSD now.

After posting the message, I managed to find the github repo, which is much more convenient for my purposes. Perhaps it could be listed on the ciao-lang site?

Both the SWI prolog and Ciao Prolog are self-hosted -- ie. the web server is written in prolog AFAIK.��

Aside: I studied Common Lisp long before I learned about prolog.�� Advanced Lisp books always have a section devoted to prolog interpreters and logic programming (especially Norvig's Paradigms in Artificial Intelligence aka PAIP or Paul Graham's On Lisp). This inspired me to study prolog and logic programming directly.�� Now I enjoy prolog as much as I do CL. But I find the various prolog projects with much better documentation.��



On Wed, Mar 22, 2017 at 5:48 PM, Adam Jensen <hanzer@riseup.net> wrote:
On Sun, 19 Mar 2017 21:58:16 -0400
GreyHat LispHacker <greyhatlisphacker@gmail.com> wrote:

> I was looking for the sources (both stable and development) for ciao
> prolog.�� I was able to get them when I connected through Firefox on
> FreeBSD.�� Yet when I tried on Window 10, (through both Firefox and Windows
> IE) I got the following:
>
> "Internal error was raised during the execution of a CGI application.
> Please contact website administrator."
>
> Anyone have an idea what is going on?

Will you provide the URL to the site/page that gave the error?

Is that typical behavior of mainstream web technology (e.g., a LAMP-stack, framework-based web-app (where the LAMP "P" might be PHP, Python, or Perl (I noticed the Lisp in your address (hello))))?

The SWI-Prolog site, for example, seems somewhat atypical : <http://www.swi-prolog.org/dogfood.html>

Is the Ciao-Prolog site[1] similarly atypical?

[1]: (mentioned by OP (missing link (URL)))



_______________________________________________
Ciao-users mailing list
Ciao-users@clip.dia.fi.upm.es
http://cliplab.org/cgi-bin/mailman/listinfo/ciao-users




--
Jose