Getting 404 status when send the request- APIGEE TRAILER

[#1]

Getting 404 error when i try to send the request .Please find the details.apigee-doc1.zip

[mdunker]

Hi @Annapurna Seeram

Your error message indicates you are trying to access the secure virtual host (https://....). Your screenshots indicate you only selected the default virtual host (http://) when you created the proxy. It is a better practice to just select secure and not default -- otherwise your requests must go across the wire unencrypted.

My recommendation is to go into your proxy endpoint XML configuration, and change

<VirtualHost>default</VirtualHost>

to

<VirtualHost>secure</VirtualHost>

and redeploy. Then make your requests via https instead of http.

[#3]

Hi Mike

Thanks a lot for your reply . I tried to change from default to secure .

now when i tried its throwing an error like

{"fault":{"faultstring":"Raising fault. Fault name : unknown-resource","detail":{"errorcode":"steps.raisefault.RaiseFault"}}}


I have one more query...
if the wsdl file contains the reference to the schemas like for ex:

<xsd:import namespace="http://www.test.com/DA/CF_Error" schemaLocation="../../../testCf/xsd/test.xsd"/>
if the wsdl file contains like this its not at all validating the wsdl file. then i tried to give complete path for the schemalocation ex :

<xsd:import namespace="http://www.test.com/DA/CF_Error" schemaLocation="http://test/testCf/xsd/test.xsd"/>

then i saved the wsdl file and select the wsdl and try to validate its throwing an error like 
Fetch WSDLError: There was an error processing the WSDL
the same WSDL is working fine without any issues with the SOAP UI.
Could you please advise.
Thanks a lot for your help.

[mdunker]

Hi @Annapurna Seeram

I haven't seen your proxy, but generally the 404 issue is because you are sending a combination of verb and path that is not supported. If you try to run from the trace tool, with trace turned on, you can explore the proxy and see what is happening.

I think the WSDL issue may stem from namespace issues. I think it will try to reach out to the namespace URL, and if it can't reach, will fail. Try removing namespace from the WSDL.