I have an ASP.NET MVC 2.0 application where I have an action that returns a jsonp action result. It worked on my development machine from my local IIS web site to another IIS site.
When I deployed the services site on Windows Server 2008 R2+IIS7.5 the ajax calls don't work and I get this error:
404 The resource you are looking for
might have been removed, had its name
changed, or is temporarily unavailable
Update: Solved
The problem was with query string limits on IIS 7.5. You can adjust this by following the steps on this page:
http://www.iis.net/ConfigReference/system.webServer/security/requestFiltering/requestLimits
The problem was with query string limits on IIS 7.5. You can adjust this by following the steps on this page:
http://www.iis.net/ConfigReference/system.webServer/security/requestFiltering/requestLimits
Related
I am having an issue with URL Rewrite feature on IIS running on Win Server 2019.
On that IIS, the web interface for Remote Desktop Services is running (smoothly).
I added two additional websites to the IIS, which should redirect to the "Default Web Site".
For simplicity, lets call the Web Sites like
ny-sales.domain.com
ny-saleslogin.domain.com
ny-salesmanagement.domain.com
All the ny-sales*.domain.com should redirect to ny-sales.domain.com.
So I installed the URL Rewrite module and added the rule like this:
(.*)ny-sales(login|management).domain.com(.*)
Action: Redirect
URL: https://ny-sales.domain.com/RDWeb
But somehow, I get not redirected at all, when typing https://ny-saleslogin.domain.com (or ...management...).
Can someone please help me investigate the problem?
Greetings, xola
Previously I was running ColdFusion 10 configured with Apache on my localhost. I am using a different machine now and I am now using ColdFusion 11's built in web server. I have imported settings from an archived ".car" file. My app uses ColdFusion Rest services which were working on my previous machine. I have setup the rest service on this new machine and I am using the same service name but with a different absolute path to directory.
for example:
previous directory: - D:/foo/bar/api/v2
current directory: - C:/foo/bar/baz/api/v2
The rest service is registered and gets refreshed successfully in the ColdFusion Administrator. But when I try to access the API path on localhost, I get this 500 error :
This page isn’t working
localhost is currently unable to handle this request.
HTTP ERROR 500
Application v2 could not be found. The specific sequence of files included or processed is: ''''
We are using WSO2 Carbon 4.2.0 through the WSO2 Application Server (AS) package. In replacing an older, highly customized Carbon installation (provided by a company that no longer supports the product, has abandoned it and refuses to work on it, and left us no details on how/what they modified in Carbon), we have deployed a couple web applications in the webapps container as they were deployed before in the older instance. We have changed our WebContextRoot in the carbon.xml from the default "/" to a sub-URL of ex: "/stuff", as is also detailed in the self-answered SO question here. However the answer given there is not detailed in what the OP actually encountered when he modified his WSO2 instance.
In testing the above configuration we noticed that if a user were to go to a non-existent web address on the server, depending on the format of the URL they are either:
redirected to a blank page;
receive a "500 Internal server error" (I suspect this is the embedded Tomcat?);
get sent to the Carbon login page (which we definitely do not want to happen for security reasons); or
get an XML document stating:
<faultString> The service cannot be found for the endpoint reference (EPR) /stuff/services/nonexistantservicename </faultString>
At least in the case of missing content we wish the user to be sent to a standardized 404 error page, or at the least be sent an HTTP 404 error by the server. For services the XML error is palatable, we can deal with that.
The only option for us right now to circumvent this issue is to place a proxy in front of the WSO2 instance, which would be another layer to manage and tune, and possibly degrade performance. Please know that I am not a programmer but just an admin with DevOps experience. I would not know how to handle this with e.g. a Java solution or re-coding parts of WSO2. Customizing the core product would also hamper future upgrades of WSO2, a scenario we are trying to dig ourselves out of now as detailed above. Is there no internal WSO2 mechanism to handle non-existent content? Can we not redirect any errors to a standard canned response page?
I am using SQL Server CE 4.0 with WebApi on Windows Azure Websites. I have been successfully able to deploy SQL Server CE. The weird problem I am facing is that my site is able to log me in using the same DB but I am not able to use any of the controllers to fetch the data.
I am using same connection string for both. The only difference is that for logging in I am using WebSecurity as I have enabled OAuth on the site.
Can someone throw some light on how to debug and fix this issue? The error I am getting for the calls is
Format of the initialization string does not conform to specification
starting at index 0.
However the same string works for authentication, change password, adding OAuth connections etc.
Thanks in advance
I connected to the site using FTP. I was not giving the site name as domain name and it was denying me access earlier. On connecting, I got hold of the Web.config file and I found something interesting. While publishing the site, the web.config was modified to add another connectionstring with the name of context_DatabasePublish.
This string had following details connectionString="ContextName_DatabasePublish.ConnetionString" providerName="System.Data.SqlClient"
Also there was a new section called context added to the entityframework section of the config file with all the details for the context to use but again pointing to same connection string. The provider it is using is sql and not sqlce. I believe that is the reason it was failing.
I uploaded my normal config file and the site started working. I need to explore more on to why and how the new connection string got added. I will post the details in comments.
I am using AppFabric 1.1 in IIS 7.5 on windows 7 machine to host my Workflows as service. Though I am able to see System endpoints and Application Default endpoints in AppFabric dashboard in IIS, I am not able to see my endpoints that I defined in Web.config file of the application.Also when I add Service Reference in my client projects, I can only see default endpoint configuration values provided by AppFabric. It appears that AppFabric is ignoring <'Service'> tag values in application's web.config file.What could be the reason? Is there something I might have missed ? Any suggestions are greately appreciated.
Thanks
I found the answer. When I changed the service name (in service tag element) exactly as it is in appfabric dashboard for the service, the application endpoints are showing up.