Here are some log entries from lighttpd (the first is the
successful (200) firefox request and the second is the failed
(500) chrome request):
50.xxx ss3.gemtalksystems.com - [10/Aug/2019:14:18:56 -0700] "GET
/ss/STON.html HTTP/1.1" 200 6961 "-" "Mozilla/5.0 (X11; Ubuntu;
Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0"
50.xxx ss3.gemtalksystems.com - [10/Aug/2019:14:19:21 -0700] "GET
/ss/STON.html HTTP/1.1" 500 512 "-" "Mozilla/5.0 (X11; Linux
x86_64) AppleWebKit/537.36 (KHTML, like Gecko)
Chrome/76.0.3809.100 Safari/537.36"
Seaside server logs show no errors being logged, since this morning ...)
No entries in fastcgi error log since midnight Aug 8th ...
The 500 means there is some part of the system on our machine that is choking on the Chrome http request, but at this point it sure isn't obvious (to me)...
Dale
Well, here's the html that shows up in firefox ... can anyone spot anything on this page that would cause chrome to do anything different than firefox?
<html><head><title>GTD Implementation</title></head><body onload="onLoad()"><h1>GTD Implementation</h1><a href="http://ss3.gemtalksystems.com/ss/GTDImplementation.html">SqueakSource3 project page</a><p>This project is an implementation of the GTD (Getting Things Done) practice described in David Allen's book.</p><a href="GTD-SergioFedi.20.mcz">GTD-SergioFedi.20.mcz</a><br/><a href="GTD-SergioFedi.19.mcz">GTD-SergioFedi.19.mcz</a><br/><a href="GTD-SergioFedi.18.mcz">GTD-SergioFedi.18.mcz</a><br/><a href="GTD-SergioFedi.17.mcz">GTD-SergioFedi.17.mcz</a><br/><a href="GTD-SergioFedi.16.mcz">GTD-SergioFedi.16.mcz</a><br/><a href="GTD-SergioFedi.15.mcz">GTD-SergioFedi.15.mcz</a><br/><a href="GTD-FedericoFigueredo.14.mcz">GTD-FedericoFigueredo.14.mcz</a><br/><a href="GTD-SergioFedi.13.mcz">GTD-SergioFedi.13.mcz</a><br/><a href="GTD-SergioFedi.12.mcz">GTD-SergioFedi.12.mcz</a><br/><a href="GTD-SergioFedi.11.mcz">GTD-SergioFedi.11.mcz</a><br/><a href="GTD-FedericoFigueredo.10.mcz">GTD-FedericoFigueredo.10.mcz</a><br/><a href="GTD-SergioFedi.9.mcz">GTD-SergioFedi.9.mcz</a><br/><a href="GTD-FedericoFigueredo.8.mcz">GTD-FedericoFigueredo.8.mcz</a><br/><a href="GTD-FedericoFigueredo.7.mcz">GTD-FedericoFigueredo.7.mcz</a><br/><a href="GTD-SergioFedi.6.mcz">GTD-SergioFedi.6.mcz</a><br/><a href="GTD-SergioFedi.5.mcz">GTD-SergioFedi.5.mcz</a><br/><a href="GTD-SergioFedi.4.mcz">GTD-SergioFedi.4.mcz</a><br/><a href="GTD-SergioFedi.3.mcz">GTD-SergioFedi.3.mcz</a><br/><a href="GTD-FedericoFigueredo.2.mcz">GTD-FedericoFigueredo.2.mcz</a><br/><a href="SUnit-UI-SergioFedi.111.mcz">SUnit-UI-SergioFedi.111.mcz</a><br/><a href="GTD-SergioFedi.1.mcz">GTD-SergioFedi.1.mcz</a><br/><script type="text/javascript">/*<![CDATA[*/function onLoad(){};/*]]>*/</script></body></html>This url (front page) is displayed okay in chrome (http://ss3.gemtalksystems.com/ss)...
FWIW, the following html (from GemSource: http://seaside.gemtalksystems.com/ss/PortablePetitParser/) displays just fine in chrome:<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html><head><title></title></head><body><title>PortablePetitParser</title><h1>PortablePetitParser</h1><a href="http://seaside.gemtalksystems.com/ss/PortablePetitParser.html">GemSource project page</a><p></p><a href="ConfigurationOfPetitParser-EstebanLorenzano.27.mcz">ConfigurationOfPetitParser-EstebanLorenzano.27.mcz</a><br /><a href="PetitXPath-EstebanLorenzano.5.mcz">PetitXPath-EstebanLorenzano.5.mcz</a><br /><a href="ConfigurationOfPetitParser-EstebanLorenzano.26.mcz">ConfigurationOfPetitParser-EstebanLorenzano.26.mcz</a><br /><a href="PetitParserGemstone-EstebanLorenzano.2.mcz">PetitParserGemstone-EstebanLorenzano.2.mcz</a><br /><a href="ConfigurationOfPetitParser-EstebanLorenzano.25.mcz">ConfigurationOfPetitParser-EstebanLorenzano.25.mcz</a><br /><a href="PetitParser-EstebanLorenzano.224.mcz">PetitParser-EstebanLorenzano.224.mcz</a><br /><a href="ConfigurationOfPetitParser-EstebanLorenzano.24.mcz">ConfigurationOfPetitParser-EstebanLorenzano.24.mcz</a><br /><a href="PetitParser-EstebanLorenzano.223.mcz">PetitParser-EstebanLorenzano.223.mcz</a><br /><a href="PetitParser-EstebanLorenzano.222.mcz">PetitParser-EstebanLorenzano.222.mcz</a><br /><a href="PetitXPath-EstebanLorenzano.4.mcz">PetitXPath-EstebanLorenzano.4.mcz</a><br /><a href="PetitParserGemstone-EstebanLorenzano.1.mcz">PetitParserGemstone-EstebanLorenzano.1.mcz</a><br /><a href="ConfigurationOfPetitParser-EstebanLorenzano.17.mcz">ConfigurationOfPetitParser-EstebanLorenzano.17.mcz</a><br /><a href="PetitXml-EstebanLorenzano.32.mcz">PetitXml-EstebanLorenzano.32.mcz</a><br /><a href="PetitXPath-EstebanLorenzano.2.mcz">PetitXPath-EstebanLorenzano.2.mcz</a><br /><a href="PetitJson-EstebanLorenzano.7.mcz">PetitJson-EstebanLorenzano.7.mcz</a><br /><a href="PetitCSV-EstebanLorenzano.8.mcz">PetitCSV-EstebanLorenzano.8.mcz</a><br /><a href="PetitAnalyzer-EstebanLorenzano.39.mcz">PetitAnalyzer-EstebanLorenzano.39.mcz</a><br /><a href="PetitTests-EstebanLorenzano.33.mcz">PetitTests-EstebanLorenzano.33.mcz</a><br /><a href="PetitParser-EstebanLorenzano.218.mcz">PetitParser-EstebanLorenzano.218.mcz</a><br /><a href="ConfigurationOfPetitParser-EstebanLorenzano.23.mcz">ConfigurationOfPetitParser-EstebanLorenzano.23.mcz</a><br /><a href="PetitAnalyzer-EstebanLorenzano.44.mcz">PetitAnalyzer-EstebanLorenzano.44.mcz</a><br /><a href="ConfigurationOfPetitParser-EstebanLorenzano.22.mcz">ConfigurationOfPetitParser-EstebanLorenzano.22.mcz</a><br /><a href="PetitAnalyzer-EstebanLorenzano.43.mcz">PetitAnalyzer-EstebanLorenzano.43.mcz</a><br /><a href="ConfigurationOfPetitParser-EstebanLorenzano.21.mcz">ConfigurationOfPetitParser-EstebanLorenzano.21.mcz</a><br /><a href="PetitAnalyzer-EstebanLorenzano.42.mcz">PetitAnalyzer-EstebanLorenzano.42.mcz</a><br /><a href="PetitParser-EstebanLorenzano.221.mcz">PetitParser-EstebanLorenzano.221.mcz</a><br /><a href="ConfigurationOfPetitParser-EstebanLorenzano.20.mcz">ConfigurationOfPetitParser-EstebanLorenzano.20.mcz</a><br /><a href="PetitAnalyzer-EstebanLorenzano.41.mcz">PetitAnalyzer-EstebanLorenzano.41.mcz</a><br /><a href="ConfigurationOfPetitParser-EstebanLorenzano.19.mcz">ConfigurationOfPetitParser-EstebanLorenzano.19.mcz</a><br /><a href="PetitXml-EstebanLorenzano.33.mcz">PetitXml-EstebanLorenzano.33.mcz</a><br /><a href="PetitXPath-EstebanLorenzano.3.mcz">PetitXPath-EstebanLorenzano.3.mcz</a><br /><a href="PetitTests-EstebanLorenzano.35.mcz">PetitTests-EstebanLorenzano.35.mcz</a><br /><a href="PetitParser-EstebanLorenzano.220.mcz">PetitParser-EstebanLorenzano.220.mcz</a><br /><a href="PetitJson-EstebanLorenzano.8.mcz">PetitJson-EstebanLorenzano.8.mcz</a><br /><a href="PetitCSV-EstebanLorenzano.9.mcz">PetitCSV-EstebanLorenzano.9.mcz</a><br /><a href="PetitAnalyzer-EstebanLorenzano.40.mcz">PetitAnalyzer-EstebanLorenzano.40.mcz</a><br /><a href="PetitParser-EstebanLorenzano.219.mcz">PetitParser-EstebanLorenzano.219.mcz</a><br /><a href="ConfigurationOfPetitParser-EstebanLorenzano.18.mcz">ConfigurationOfPetitParser-EstebanLorenzano.18.mcz</a><br /><a href="PetitTests-EstebanLorenzano.34.mcz">PetitTests-EstebanLorenzano.34.mcz</a><br />Other than the !DOCTYPE at the front, the two pages of html seem to similarly constructed ...
The error message that you are seeing looks like an error that _would_ be generated by the seaside server, however there are no error messages showing up in the seaside server logs ... (other errors _are_ showing up, but the last seaside server log is from 11 am this morning (it's 2pm right now) ... I'll need to dig through some logs to see if I can find record of "the system administrator" being notified:)
Dale
On 8/10/19 8:40 AM, Sergio Fedi wrote:
Ok, strangely, when I go to that page in Firefox it doesn't show that error.Tried to go with Chrome in incognito (so as to get rid of plug ins) and it still fails.
Gonna try from within Pharo and if it fails I'll post again.
Below are screenshots on how it fails or succeeds on each browser.
In firefox:
<image.png>
In chrome:<image.png>
On Fri, Aug 9, 2019 at 10:30 PM Paul DeBruicker <pdebruic@gmail.com> wrote:
Also did you use the URL of the page your repo is on? Seems like maybe you
did from the image. You shouldn't.
You should use the Monticello Repository specification shown on the repo
page when you hover over Monticello Repository in the Getting The Code
section of the project page on ss3.
e.g.
MCHttpRepository
location: 'http://ss3.gemtalksystems.com/ss/GTDImplementation'
user: ''
password: ''
Paul DeBruicker wrote
> what is the repo you're having trouble reading?
>
>
> Sergio Fedi wrote
>> Hello,
>>
>> I'm coming back after a few years (Pharo 5.0) and tried to take a look
>> and
>> download some projects I have on ss3.
>>
>> I'm using a Pharo 7.0 image.
>>
>> Going to the ss3 site I find that I can't access my projects, a "Reading
>> a
>> number failed: a digit between 0 and 9 expected" error shows in the page.
>>
>> Trying to view them from Monticello, after adding the appropriate
>> repository it shows weird characters for the name and versions and it is
>> unable to load them.
>>
>> [image: image.png]
>>
>> What am I missing/doing wrong?
>>
>> Thanks!
>>
>>
>> image.png (182K)
>> <http://forum.world.st/attachment/5102137/0/image.png>
>
>
>
>
>
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html