¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Downloads and Web Updates


dvd_fenlon
 

When I try to get the current Sun image or do a web update I get an
error message saying "http get: Can not find IP of xxx Try entering IP
directly"
I can access the wwwsoho page and the celestrak and cfa-www pages by
web browser but not through xephem.
The asteroid data set downloads both work O.K. through xephem.

Any ideas ?


Roland Roberts
 

dvd_fenlon wrote:
When I try to get the current Sun image or do a web update I get an
error message saying "http get: Can not find IP of xxx Try entering IP
directly"
I can access the wwwsoho page and the celestrak and cfa-www pages by
web browser but not through xephem.
The asteroid data set downloads both work O.K. through xephem.
I don't understand how (1) the cfa-www pages don't work through XEphem, but (2) you can download the asteroid data sets okay through XEphem.

I do know that cfa-www does a redirect to the new www.cfa name and that XEphem won't handle that. Look at the URL after you have reached it through your browser. Is it the same one you typed in? If not, you've been redirected.

roland

--
PGP Key ID: 66 BC 3B CD
Roland B. Roberts, PhD RL Enterprises
roland@... 6818 Madeline Court
roland@... Brooklyn, NY 11220


dvd_fenlon
 

--- In xephem@..., Roland Roberts <roland@...> wrote:

dvd_fenlon wrote:
When I try to get the current Sun image or do a web update I get an
error message saying "http get: Can not find IP of xxx Try entering IP
directly"
I can access the wwwsoho page and the celestrak and cfa-www pages by
web browser but not through xephem.
The asteroid data set downloads both work O.K. through xephem.
I don't understand how (1) the cfa-www pages don't work through XEphem,
but (2) you can download the asteroid data sets okay through XEphem.

I do know that cfa-www does a redirect to the new www.cfa name and that
XEphem won't handle that. Look at the URL after you have reached it
through your browser. Is it the same one you typed in? If not, you've
been redirected.

roland

--
PGP Key ID: 66 BC 3B CD
Roland B. Roberts, PhD RL Enterprises
roland@... 6818 Madeline Court
roland@... Brooklyn, NY 11220
I have changed the cfa pages names in XEphem to www.cfa but those and
the celestrak pages still will not work.
The asteroid data does not have a web address visible only a description.
My main concern is the current Sun image.
If it is necessary to enter the IP address directly then where is it
entered ?
I have greped and only found sohowww in the xephem binary file in
/usr/local/bin !


 

On 1/6/09 11:24 AM +0900, dvd_fenlon wrote:

I have changed the cfa pages names in XEphem to www.cfa but those and
the celestrak pages still will not work. The asteroid data does not
have a web address visible only a description. My main concern is the
current Sun image. If it is necessary to enter the IP address
directly then where is it entered ? I have greped and only found
sohowww in the xephem binary file in /usr/local/bin !
No doubt this is not at all going to be helpful, but all of the file 'gets' work fine in my 3.6.3 under OS X Tiger. I checked the sun images this morning and all was well.

trane
--
/////////////////////////////////////////////////////////
// Trane Francks trane@... Tokyo, Japan
// Practice random kindness and senseless acts of beauty.


 

On 01/06/2009 10:54 PM, Trane Francks wrote:
On 1/6/09 11:24 AM +0900, dvd_fenlon wrote:

I have changed the cfa pages names in XEphem to www.cfa but those and
the celestrak pages still will not work. The asteroid data does not
have a web address visible only a description. My main concern is the
current Sun image. If it is necessary to enter the IP address
directly then where is it entered ? I have greped and only found
sohowww in the xephem binary file in /usr/local/bin !
No doubt this is not at all going to be helpful, but all of the file
'gets' work fine in my 3.6.3 under OS X Tiger. I checked the sun images
this morning and all was well.

trane
Just to say that www.cfa is not a FQDN (full qualified domain name)
at all and leads you on a bloody Commercial financial garbage site :-D

For us we have no problems with recommended addresses like:



.... and hard coded one for SOHO images ....

Best regards
Serge.

--
"The surest sign that intelligent life exists
elsewhere in the universe is that it has
never tried to contact us."
???Bill Watterson
--------------------------
Serge Montagnac

obs-psr@...
--------------------------


 

Version 3.7.7, fresh download and compile. Fedora 24, x86_64.?MOTIFL = /usr/lib64

Try to download latest SOHO image (same results for any image or size) and?sohowww.nascom.nasa.gov replies (from the log):
Rcv: <p>The document has moved <a href="https://:443/data/realtime/eit_284/512/latest.jpg">here</a>.</p>

I messed around with sunmenu.c and?XEphem.SOHOhost until the GET matched what sohowww claimed:

http: GET https://sohowww.nascom.nasa.gov:443/data/realtime/eit_284/512/latest.jpg HTTP/1.0
User-Agent: xephem/3.7.7

Rcv: HTTP/1.1 302 Found
Rcv: Date: Sun, 06 Nov 2016 16:27:36 GMT
Rcv: Server: Apache
Rcv: Location: https://:443/data/realtime/eit_284/512/latest.jpg
Rcv: Content-Length: 233
Rcv: Connection: close
Rcv: Content-Type: text/html; charset=iso-8859-1
Rcv: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
Rcv: <html><head>
Rcv: <title>302 Found</title>
Rcv: </head><body>
Rcv: <h1>Found</h1>
Rcv: <p>The document has moved <a href="https://:443/data/realtime/eit_284/512/latest.jpg">here</a>.</p>
Rcv: </body></html>
Error talking to SOHO .. see File->System log

Looks like something changed on the sohowww end or there is something platform-specific about httpGET. That href looks suspicious, doesn't it??

XEphem.SOHOhost: ?sohowww.nascom.nasa.gov sends a request that completes.?XEphem.SOHOhost: ?sohowww.nascom.nasa.gov:443 fails before the request can complete, so the :443 had to go into 'fn' or 'get'

I hope this information is of use to somebody.



 

What was an HTTP request is now an HTTPS request, which is why you see port 443 referenced, and the prefix changed.? This change happened some time ago, I think it was a couple years.

There are several workarounds, depending on your linux sophistication.? In essence they all work thru a local HTTP server to appear to XEPHEM appropriately, and actually passthru a fetch via HTTPS.? Thus all of the pita HTTPS effort moves into an external program.

If you just want images, 'wget' works fine.? If you want to complain, ask SOHO why a fully secure transaction is needed to fetch an image.


 

"No doubt this is not at all going to be helpful, but all of the file
'gets' work fine in my 3.6.3 under OS X Tiger. I checked the sun images
this morning and all was well.

trane"

You should check the date on the image, I get one from several years ago just fine.


 

Check the "User contrib" area, there is a patch for using openssl to access SOHO.

Elwood