Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 14 years ago.
Improve this question
I'm at my wit's end here. I'm trying to use an auto-complete extender from the asp.net ajax extensions toolkit, which is filled from a bog-standard webservice. The application is a .net 3.5 web site, hosting the webservice in a subdirectory (real, not virtual).
Whenever I try to post to the webservice I get the following error:
The HTTP verb POST used to access path '/Workarea/webservices/FindAdvisorNameService.asmx/FindAdvisorName' is not allowed.
To complicate matters, a co-worker of mine pulled down the solution and can run it fine.
After doing some Googling, it seems that there are some issues with URL rewriting, so I had him try using my web.config -- he still has no problem, and I still have no success.
Anyone have any thoughts on what could be up, or where to start looking?
To complicate matters, this is an Ektron CMS400.Net solution, but he has the same version of Ektron installed that I do. The project was recently upgraded from the 2.0 to 3.5 framework, but still, it's in 3.5 on his machine as well.
I've checked the IIS mappings, and GET, POST, and DEBUG are allowed on ASMX files.
Help me Obi-Wan KeSObi, you're my only hope!
Edit: Oh, yeah, to complicate matters, this is a brand new machine I have, so there's not likely to be that much weird stuff in the registry, etc. etc.. The co-worker's machine is almost as new.
Ok, found the issue with the help of a colleague. Seems the Ektron CMS added a mapping in IIS -- it mapped * to aspnet_isapi.dll. That overrode all the other mappings. I deleted that, and now things work.
Are you rewriting URLs? You need to exclude your web services from rewrites.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
Apologies if this is in the wrong category. I'm currently developing and application in ASP, due to my inexperience with ASP I'm worried about vulnerabilities that a user can exploit.
My application is being coded from scratch, no templates used or defaults from Visual Studio, completely blank projects. The user is greeted with a login page where depending on there user access in active directory depends on which pages the user can access.
The exploit I'm worried about is if the user will be able to commit a directory traversal and access a page in which they're not allowed to access and change critical information.
I'm afraid my inexperience has caught up with me. Could someone explain to me how I could limit the access to the user or, If I'm over thinking the process, correct me? Constructive criticism is accepted.
Microsoft does try to help protect your application through their defaults, so if you're running in IIS, make sure the user the application pool is running under only has write access to the folders it needs to write into.
This is a very open-ended question and depends on many factors such as version of .net, server OS/IIS version, other handlers installed, etc. But a good start is to review the OWASP Top 10:
https://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project#OWASP_Top_10_for_2013
Here's a list of some automated tools you can use for testing your implementation:
https://geekflare.com/online-scan-website-security-vulnerabilities/
Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 8 years ago.
Improve this question
I am redesigning my company's website. I am not a developer, but have learned as I went along. I am ready to push out my site to a test subdomain, but I can't figure out how to publish it correctly using VS Express for Web 2013. I have multiple problems.
First, we have our own internal IIS server and I have a "site3" folder on the server ready for testing the new site. I can't use Web Deploy or Web Deploy Package. I publish using File System. This seems to sorta work, but no images load and it redirects me to a Login page that I have no intention of using. When I run the site on my local machine, everything works 100% fine - no login page and all site resources load and function perfectly.
Second, when I try to publish, there is no "Release" configuration like I see in online tutorials and MSDN, only "Debug." Is there something I'm missing in the configuration? The publishing? Am I using the wrong framework? This is my first rodeo and I am completely lost.
If anyone wants to look at my completely jacked up site, it's http://site3.tcns.net
EDIT: I'm beginning to think that it has something to do with the fact I have no clue how to configure the web.config file and the default file isn't plug-and-play for a basic website.
I have some idea as to what happened. I accidentally created an MVC solution instead of a basic website.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
Can i upgrade my existing website from asp.net framework 2.0 to 4.0, is there any harm in doing that? and if i can do that without harming my current website than please tell me the required steps to achieve this target.
thanks in advance.
There are some breaking change if you move to asp.net ver 4
Meaning that you may need to change few things, and evaluate all the pages to see that they still working the same way.
I've always updated my projects through using newer versions of Visual Studio. So for example I'd quite a few projects created in VS 2005 which I then opened in VS2010. VS prompted me to upgrade to the newer .net version and took care of the process for me. Never caused any problems although I stopped it from messing with the web.config etc. which it asks about after doing the conversion.
You should have no big issues except for web.config entries specific to .NET 2.0.
On your application server, you may need to set "Classic mode" insted of "Integrated pipeline" if you experience further issues.
There's no harm in trying. There may be some changes required to your code. Just create a copy of your existing code and attempt to upgrade the copy. Based on that, the decision to go forward with an upgrade is up to you.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I'm an asp.net developer, but I haven't found a good workflow for deployment. Especially for small quick fixes that might not even require compiling.
The way I work now is to have two VS instances up while copy pasting a lot of code and files between the project and the folder on the IIS server. Is there an automated process that moves changes as I save in the VS project?
Generally speaking, what you are doing is a pretty big no no for a lot of reasons.
When you make changes one of the big advantages ASP.Net has over something like PHP is simply that obvious problems (like misspelling a variable name) are caught during the build phase. This is a huge benefit.
Next, if you are simply modifying a file and copying it's content to the server then it sounds like you are doing your testing in production instead of leveraging your local debugger. Again, very bad practice.
Finally, VS includes a publish command. The purpose of this is to compile and publish your site to the server. It can do so through the regular file system, FTP, web deployment packages or even FPSE. That last one is NOT recommended and is probably kept for backwards compatibility only.
Point is, develop and test locally. When your ready for it to go to the server, use the publish command.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I want to create a Website for that I am using asp.net technology,Since I am Actually Buying a domain and web hosting space for it. Before that I have question regarding some doubts.
I have seen Website http://www.bigrock.in/ . As everyone Knows that Asp.net is platform dependent and I want my Website should open everywhere with same look and feel. And Someone have told me there will be no issue for platform Dependency,You only need to choose Server with windows and deploy Your website there. and after that everybody will be able to open website with same look. Now My question is that if that's the thing is there then why the issue of platform Independent for(java EE,Php) website is there.
Please Clarify my doubts.
Platfrom independence in this case is only a concern for the server, not the client.
A normal asp.net website can be openened in all mainstream browsers, on Mac, Linux or Windows or mobile clients. So it will work everywere.
ASP.net is platform dependent.
This is not true.
An asp.net website can be installed on any web-server provided it has .net framework installed on it. Most modern age windows servers has it. Hence, whoever told you that
choose Server with windows and deploy Your website there. and after
that everybody will be able to open website with same look
Is right.
When somebody accesses your website's page asp.net generates HTML content which is sent to client which is platform independent. Hence all clients will get same look and feel.