HTTP Error 404.19 - Not Found in IIS 8.5 - http-error

I have a website, which runs perfectly in IIS 7.5. but the same site with same configuration is not working properly in IIS 8.5. i am passing an system string variable in URL and it shows me
HTTP Error 404.19 - Not Found error.
So i am not able to catch the exact issue. All things are same for both IIS except IIS version only. So i need your thoughts for the problem. So that I can also look into this. Unfortunately I am new in .net, so need basic answer(s). Thanks.
If I pass "&system=value1"in URL for IIS8.5 then it stops working, even this also didn't generate any log for this. So please help me for this.
I just Came to know that if i use "sys" word in Query String then its giving error. How to avoid this issue now?

This can be found in IIS under Request Filtering. Usually, you will see this under the Deny String section of a rule, possibly one meant to thwart SQL Injection attacks.

Related

Error: 404 The page you're looking for could not be found (gitlab). How to resolve it?

Let's say I have some website with the name website.eu. When I deploy it and try to get access to a page online like this website.eu/about I catch the error:
"404 The page you're looking for could not be found. The resource that you are attempting to access does not exist or you don't have the necessary permissions to view it"
When I click on the link that brings me a website.eu/about it works well, but trying to type that URL in the input field it fails.
Everything works fine locally.
The project is developed using Vue3.
The project is no GitLab.
If someone helps I would appreciate it.
Hard to tell without seeing the code, but my guess is your router setup uses the web history mode, which relies on the server to have certain settings applied.
I believe switching to hash mode (while adding # to the routes) will work.
Alternatively, you can update your server to support redirects to have the html mode work.
example server configurations

Post csv content to Web Api

I have a c# console application which post .csv content to a web service. If I run my solution through VS, it runs perfectly fine but after deploying web service on IIS I keep getting Multiple Choice Status Code 300 error. Not sure how to resolve that. Any pointers would be appreciated.
Thanks
These are relatively simple but I cannot think of other possibilities based on your description.
One of my recent designs had a literal in the code that when I deployed it ended up using a different port which I had forgotten to change to a relative reference.
If not that then the other problem I had with it was because I used JSON to link to the web service. While it worked when viewing in VS when deployed my JSON reference was actually incorrect. specifically it had to do with code in my web.config file, which would be the app.config file for your console application. I had used the code
standardEndpoint helpEnabled="true" automaticFormatSelectionEnabled="false" crossDomainScriptAccessEnabled="true"
when I should have also added
defaultOutgoingResponseFormat="Json"
to make the code work

SugarCRM CE smarty error after upgrade

I recently upgraded our SugarCRM CE form 5.x to 6.2.6. I had some uphill experience but I overcome everything except one issue.
The following error appears in the "Email Address" area on Contact, Opportunity and other similar pages.
Warning: Smarty error: unable to read resource:
"include/SugarFields/Fields/Base/detailViewFunction.tpl" in
/home/campusre/public_html/sugar/include/Smarty/Smarty.class.php on
line 1095
I did a search on SugarCRM forum and I found only one similar thread that was old and not answered. I also contacted our hosting company to check if this problem is related with the file or folder permission but they confirmed that it is not the problem in this case.
I am a developer but didn't do any SugarCRM and Smarty development before. I am investigating the code by my self but without success so far.
Any suggestion will be highly appreciated.
Thanks in advance.
unable to read resource: include/SugarFields/Fields/Base/detailViewFunction.tpl
This usually means that incorrect permissions are set on this file or that the file doesn't exist. However, in this case it looks like a casing issue. The file is actual camel case and named DetailViewFunction.tpl. It looks like you are running into a case-sensitive issue. My initial guess is that it is due to an old module or piece of code from 5.x.

IIS 6 Parameterized Redirects

It looks like there's a way to, in IIS 6, do the following:
Redirect http://mydomain.com/old_page.asp?oldparam=111 to http://mydomain.com/new-page/111
But, I'm not sure how best to achieve this.
I'm reading up about using VBScript to access the MetaBase to set this up as shown on this page http://msdn.microsoft.com/en-us/library/ms525728%28v=vs.90%29.aspx, but so far I've had no luck. The documentation seems to assume and advanced user... I need something a little more novice.
(Also you seem to be able to use the Active Directory version or WMI version in VBS - I don't know either of them)
Any ideas?
Regards,
Jacques

Apps>Menu>Basic 405 Method Not Allowed

I am hosting my pages on my doamain. I put the following info. When I go to view the app it shows 405 Method Not Allowed..Not sure what I am doing wrong.
*
The first page load a APP makes is a POST request.
Seems your server could be rejecting them.
Its worth checking the server side error log for further information.
Indeed, it will most probably be a setting on your server. I had the same problem, my server didn't allow POST method on .html pages, changed my canvas page source to .php and all works fine now.
If you can look at your apache logs, it will provide a more clear error that we can help you debug with. Though a 405 error typically signifies a problem with the server and usually stems for a POST request.
I have made the mistake 2 times of creating my site in html instead of using a scripting extension. For example, if you are running on a Windows server and coding in Visual Studio, it is tempting to just create .htm or .html files. However, most web servers will not allow a POST operation to these pages. Instead, create .aspx pages, which will still allow you to use the same exact static HTML and JavaScript. This solved my problem in both cases.