Regarding your question "Can anyone give me guide to check how to test proxy is working properly". You can open a browser, type in the URL "http://host/proxy.ashx?your_print_service_url" to see if the print service rest end point shows up.
Hi Jian
Thank you very much for reply. But, just wanted to ask, the url format you provided has "host", is this hostname or localhost
or the name of the machine. or host is default for all computers.
this may be silly question, but wanted to be clear.
Regards
Ganesh
Hi Jian
I tried with localhost instead of host, http://localhost/proxy/proxy.ashx?yourprintserviceurl
and I am getting the following error from the browser. From the error message, it says proxy.config file is not found, although I have installed the proxy in the C:\inetpub\wwwroot\proxy, where it has proxy.ashx and proxy.config files. Any idea why it is causing problem please. The other possibility is that, since my application runs from visual studio, it is using the Asp.net built in web server and I am not sure to check whether it is running from IIS or ASP.net server.
If I use host, http://host/proxy/proxy.ashx?yourprintserviceurl, the browser ask me to check the host correctly.
Proxy.config file does not exist at application root, or is not readable.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.ApplicationException: Proxy.config file does not exist at application root, or is not readable.
Source Error:
The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:
1. Add a "Debug=true" directive at the top of the file that generated the error. Example:
<%@ Page Language="C#" Debug="true" %>
or:
2) Add the following section to the configuration file of your application:
<configuration>
<system.web>
<compilation debug="true"/>
</system.web>
</configuration>
Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.
Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.
Stack Trace:
[ApplicationException: Proxy.config file does not exist at application root, or is not readable.]
proxy.getTokenFromConfigFile(String uri) +503
proxy.ProcessRequest(HttpContext context) +140
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +913
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +165
Please help....................
Regards
Ganesh