I have an intranent application that gets iframecall.axh errors when deployed. It if I change the script manager paths to point back to a development box.(?).
Debug error message: "A web request made using the iframe executor failed. Make sure that the app's web.config registers iframecall.axd"
What am I missing? Something must need to be done to these test machines to deploy.
The http handler is set :
<addverb="*"path="iframecall.axd"type="Microsoft.Web.Services.IFrameHandler"validate="false"/>
Each of the Web Methods.
WebOperationAttribute(true,ResponseFormatMode.Json,true)
Why does Atlas use the header name and the port to call its self? I found the cause of the problem. Its appears that since we use a CSS ( type of cysco router ) to route traffic on shared servers that the call to the service is using the host header and the port which when re-routed back to the server is incorrect. If the site is available on http://<server>:<port> but the users calls it with the host
headerhttp://<host header> the call back to iframecall ishttp://<host header>:<port>
Here is an example: http://MySite/service1.asmx if hosted onhttp://MyServer:8040/service1.asmx gets called viahttp://MySite:8040/service1.asmx and fails.
Is there a work around for this or how do I fix it?
No comments:
Post a Comment