--- Begin Message ---
- To: John Caron <address@hidden>, address@hidden
- Subject: F-TDS URLs fail behind proxy with "bad URL extension" page...
- From: Roland Schweitzer <address@hidden>
- Date: Tue, 20 May 2008 15:47:45 -0500John,
We're pretty desperate for your help on a problem we're having with F-TDS. It's going to sound a little crazy, but I will try to explain the problem and a quick test you can run.
You won't need to run our IOSP code or set up Ferret because the issue manifests itself in the TDS code before any DataSource or IOSP attempts to handle the URL.
Simply put, F-TDS works when connecting directly to Tomcat, but fails when connecting to the same resource through an Apache proxy. When connecting via the proxy TDS rejects the URL as not having one of the recognized extensions. It's as if the Apache proxy munges the URL just enough that TDS gets confused. It's possible that these URLs violate some forty-eleven rules about how a URL should be constructed, but Tomcat likes them. :-)
To reproduce set up a TDS and proxy it via Apache. Suppose you did that on test.unidata.ucar.edu the set up and test would look like this:
Allow from All
The URL below that connects directly to your Tomcat will fail for you with some sort of "resource not found" error since you don't have the DataSource code, ISOP or the data. But it works on our system with the proper host and port number that connect directly to tomcat.
The same URL accessed via the proxy (without the port number) will fail with a " The URL extension did not match" page which is a response from TDS long before the DataSource and IOSP get a chance to handle the URL.
Let me know if there is some other thing we can do to help figure this out.
--- End Message ---
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.