 |
 |
On Mon, 18 Dec 2017, Nino wrote: > Thanks Peter, I tried to load the VO services, but GAIA crashed then. > That may be a total different issue though. In fact any VO request or TAP causes that. > The "browsing catalog directory" also reports an error. Hi Nino, when you say crashed, do you mean closed and disappeared from your screen? If not did you see any error messages. BTW, the VO query that I tried is: Data-Servers->Query a VO catalog server... I then used "USNO" as a substring filter and picked the CDS I/284 catalogue. All under Linux, I'm afraid if this is a Mac problem, I may not be of much help. > Should I just submit a new message to the mailing list? Often a good idea to keep the subject related to the topic. Cheers, Peter. > > On Mon, Dec 18, 2017 at 9:17 AM, Peter W. Draper <[log in to unmask]> wrote: > On Fri, 15 Dec 2017, Peter W. Draper wrote: > > On Fri, 15 Dec 2017, Antonino Cucchiara wrote: > > Hello, I recently upgraded to MacOSX and installed the STARLINK software (2017A). > I used GAIA on a daily basis before, but now I cannot load any CDS catalog or image: > in the case of, for example 2MASS J images from the archive, I get the following error: > "Error: unknown preview data Content-type text/html, charset=iso-8859-1" > > If I try to load the USNO B1 from CDS (or any CDS catalog) the search engine runs with no result. > Some CADC works and ESO catalogs as well. > > Reverting to previous version of the software does not solve the issue, that is why I am thinking it > may be due > to some OS changes. > > Thanks for your help, > > > Hi Nino, > > there does seem to be something odd going on with these requests, and they are failing for me as well. I'll have > a look into this, but it may take a little while... > > > Hi Nino, > > the problem is caused by GAIA sending non-standard HTTP headers to the CDS. Previously this was acceptable, but that format > is now seen as a possible security issue, if very interested see: > > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-8743 > > (simply Skycat was using \n as a newline when \r\n is strictly required in the HTTP standards). > > I've fixed this problem, but getting a fix out will require some help from the EAO, who are now providing the releases of > GAIA/Starlink. In the meanwhile all I can suggest is that you try out the VO services. USNO B1 is available, and working, in > those. > > Thanks for alerting us to this issue, > > Peter. > > ---- > Starlink User Support list > For list configuration, including subscribing to and unsubscribing from the list, see > https://www.jiscmail.ac.uk/cgi-bin/webadmin?A0=STARLINK > > > ---- Starlink User Support list For list configuration, including subscribing to and unsubscribing from the list, see > https://www.jiscmail.ac.uk/cgi-bin/webadmin?A0=STARLINK > -- Peter W. Draper, http://astro.dur.ac.uk/~pdraper ---- Starlink User Support list For list configuration, including subscribing to and unsubscribing from the list, see https://www.jiscmail.ac.uk/cgi-bin/webadmin?A0=STARLINK