15,797,683 members
Sign in
Sign in
Email
Password
Forgot your password?
Sign in with
home
articles
Browse Topics
>
Latest Articles
Top Articles
Posting/Update Guidelines
Article Help Forum
Submit an article or tip
Import GitHub Project
Import your Blog
quick answers
Q&A
Ask a Question
View Unanswered Questions
View All Questions
View C# questions
View C++ questions
View Javascript questions
View Python questions
View PHP questions
discussions
forums
CodeProject.AI Server
All Message Boards...
Application Lifecycle
>
Running a Business
Sales / Marketing
Collaboration / Beta Testing
Work Issues
Design and Architecture
Artificial Intelligence
ASP.NET
JavaScript
Internet of Things
C / C++ / MFC
>
ATL / WTL / STL
Managed C++/CLI
C#
Free Tools
Objective-C and Swift
Database
Hardware & Devices
>
System Admin
Hosting and Servers
Java
Linux Programming
Python
.NET (Core and Framework)
Android
iOS
Mobile
WPF
Visual Basic
Web Development
Site Bugs / Suggestions
Spam and Abuse Watch
features
features
Competitions
News
The Insider Newsletter
The Daily Build Newsletter
Newsletter archive
Surveys
CodeProject Stuff
community
lounge
Who's Who
Most Valuable Professionals
The Lounge
The CodeProject Blog
Where I Am: Member Photos
The Insider News
The Weird & The Wonderful
help
?
What is 'CodeProject'?
General FAQ
Ask a Question
Bugs and Suggestions
Article Help Forum
About Us
Search within:
Articles
Quick Answers
Messages
Comments by Tomz_KV (Top 3 by date)
Tomz_KV
27-Apr-18 15:25pm
View
My issue was similar to yours. Everything worked fine in dev environment. It was also fine when the web api was hosted in production and called from a dev asp.net app. 401 unauthorized error only occurred when the web api and the app were both run on production server. Windows authentication was used for both. The fix (or workaround) was to call the web api using its IP address instead of a friendly url. This might not be a favorable way to do it since the IP address did not have a SSL certificate.
Can you share how you resolved your issue?
Tomz_KV
3-Jan-12 15:05pm
View
Deleted
It might be better to redirect to a html page instead of .aspx page during maintenance. app_offline.htm does not need any code. If you want to say something different to different users, you do need .aspx page.
Tomz_KV
15-Jul-10 14:38pm
View
There is one attribute in page directive: validateRequest. The default value is true. If you set validateReqeust="false", user will be allowed to enter html code.