WSDL Url monitor issues
Hi Friends, I am facing some weird behaviour from F5 while using health monitor for wsdl url. I am using the health monitor as follows Send String: GET /app/xyz/AdminService.wsdl HTTP/1.1\r\nHost: myapp.myname.com \r\nConnection: Close\r\n\r\n Revieve String: HTTP/1.1 200 OK Health monitor works fine but the end server is loaded with so many HTTP 500 error while F5 performing health checks. I have verified and found the wsdl respond back with a complete x ml page and this xml page contains url which in turn give HTTP 500 Error. How can we solve this issue? Any idea? -Jinshu
XML and WSDLs
Hello All, Is there a way for the BigIP to exposed the WSDLs when a client request them instead of the backend server. I have set a Security Policy, a XML profile and installed the WSDLs needed. I had a former infrastructure with IBM Datapower from where this was possible, I wonder if this is possible with the ASM module Customer request is like this GET /foobar-webservices/test?wsdl HTTP/1.1 Host: foo.bar:443 Connection: close Thank you.
BIG-IP : iControl : System/ConfigSync::download_configuration() : error opening file for read operations
BIG-IP 11.4.1 Build 608.0 Final VE I'm in .NET 4.5 C : using proxy classes generated from WSDL, I call into iControl API to retrieve BIG-IP system configuration : var systemConfigSync = new SystemConfigSync("bigip", "admin", "admin", 600000); long offset = 0; SystemConfigSyncFileTransferContext context = systemConfigSync.download_configuration("bigip", 131072, ref offset); throws exception : Exception caught in System::urn:iControl:System/ConfigSync::download_configuration() Exception: Common::OperationFailed primary_error_code : 16908289 (0x01020001) secondary_error_code : 0 error_string : Error opening file for read operations On v11.4.0 , this call successfully retrieved the system configuration ( bigip.conf ). However, on upgrading to 11.4.1 it began failing.ASM : XML profile and WSDL filtering
Hello All, I have a Security Policy to filter XML using a WSDL. The XML filtering is working fine when a client is not following the WSDL. My question is related to the answer made from the backend server. From time to time the backend server is sending an incorrect xml answer, the xml is not formated properly or incomplete. The issue here is that the client is receiving incorrect xml trafic and the ASM is not filtering it. Is it a normal behavior ? Is there a way to enforce the trafic send from the backend server to the client depending on the WSDL and not only when the client is requesting data ? Thanks for you help RegardsASM : WSDLs and Allowed URLs List
Hello, I'm using ASM module to filter XML traffic with WSDL file. I have an issue with serval security policy. When creating an XML profile, i import an WSDL file and automatically there is an URI added in the Allowed URLs List based on the soap address location of the WSDL. But now i have URIs which are not related to soap address location and now present in the WSDL file. I would like to know how is the Allow URLs List is actually working because from what is see it's now only based to on soap address location. Does anyone has more information about this ? Is there a way to disable the automatic import of the soap address location from the WSDL file to the allowed urls list ? Thank you for your help.