NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Hi Kevin:Do you see a problem using the https? Forcing a redirect just doubles the # of round trip messages between client and server.
John On 7/29/2013 3:42 PM, Kevin Manross wrote:
Howdy, I have the data access on my TDS secured via redirect through 8443. When an authorized user visits the OPeNDAP Access Form after successfully meetig the challenge, the Data URL has the SSL syntax, in my case: https://castle.ucar.edu:8443/thredds/dodsC/ds083.2/best However, most of the OPeNDAP clients I have tested with seem to work best when providing the non-SSL http://castle.ucar.edu/thredds/dodsC/ds083.2/best and the client handles the redirect. Is there a way I can change the Data URL to the non-URL veresion to avoid confusion on the part of our users? -kevin. -- Kevin Manross NCAR/CISL/Data Support Section Phone: (303)-497-1218 Email:manross@xxxxxxxx <mailto:manross@xxxxxxxx> Web:http://rda.ucar.edu _______________________________________________ thredds mailing list thredds@xxxxxxxxxxxxxxxx For list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/
thredds archives: