Select to view content in your preferred language

csw-client can't get records over internet

1516
2
08-29-2011 06:17 AM
markusbesenfelder
New Contributor
hi everybody,

I have installed the csw-client for arcgis 1.0.14 in ArcMap10/sp1. I created the custom xsl-scripts for our catalog and everything works fine! but it just works with the catalog that is located in our intranet and I would like to speak with external catalogs as well.

If i try to request a catalog in the internet, i.e. the built-in GOS2 OGC Core Catalog I will get the prompt "Enter Credentials". But the proxy-settings are set correctly, the client gets the capabilities without problems (I see them in the log), but when it gets to the getrecords-request-query the client asks for username and password. This is really confusing. If I post the request via browser everything works fine - without password.
So I checked the following:

1. the Internetconnection of arcmap: I get the capabilties of the catalogs, i can connect to arcgis online and in the proxy-settings in arccatalog are set to the systemsettings.  

2. the getrecords request: works fine in the intranet and via browser in the internet.

3. the firewall: windowsfirewall is turned off.

has anybody an idea what i could try to get it working? It would be great if at least the built-in catalog would be working...

cheers

markus
0 Kudos
2 Replies
PrestigeMakanga
Deactivated User
I also have the same problem even for data that is on my intranet. Did you manage to find a solution?

Regards
Prestige
0 Kudos
markusbesenfelder
New Contributor
I also have the same problem even for data that is on my intranet. Did you manage to find a solution?

Regards
Prestige


In the End I found out that the Problem was a definition within our proxy-server. A script to implement a "pornfilter" supressed the Post-requests of ArcMap.
If you can't get access to data even on the intranet and the logfiles of the cs-w client don't help, i would suggest a sniffer-tool like wireshark or httpdebugger to monitor the in- and outgoing http- traffic. Thats the way i found out what the problem was.

good luck...

markus
0 Kudos