| M | T | W | T | F | S | S |
|---|---|---|---|---|---|---|
| « Jan | Apr » | |||||
| 1 | 2 | 3 | ||||
| 4 | 5 | 6 | 7 | 8 | 9 | 10 |
| 11 | 12 | 13 | 14 | 15 | 16 | 17 |
| 18 | 19 | 20 | 21 | 22 | 23 | 24 |
| 25 | 26 | 27 | 28 | 29 | ||
Will It Fly? How to Know if Your New Business Idea Has Wings...Before You Take the Leap

Posted: Tuesday, February 19th, 2008
Category: ASP .Net
Author: Wahyudi
I was having a trouble assigning SSL to only a specific page inside an ASP .Net web application. We usually set a custom 403 page in IIS to other application, and we always do this in application level. But for only one page we found a problem since in the Web.config “CustomError” part, we didn’t add custom error page for 403. So just to make sure, if you do a redirection in IIS to solve 403 error, add that redirection in your Web.config as well and most important is to set the SSL in directory level. So if your page inside a parent folder under the root folder, set the SSL in that parent folder.