I'm running an Asp.NET MVC 2 app under IIS 6.All pages are behind Windows Integrated Authentication except for some pages that accepts anonymous access.We setup these pages in the web.config with the location element like this
this is an Asp.NET MVC app, the path indicated in the path attribute points to an action method not a physical location.When this was running under IIS 7 integrated mode it was working fine. But when we switched to IIS 6 we get the login prompt even with the pages that are set to accept anonymous users.ow to make IIS 6 authorize anonymous access to non physical paths ?
I have a website say www.abc.com I am giving the users there own mini site with the URLwww.abc.com/website/home.aspx?UID=1
This URL will access to my Home.aspx page located in website folder and display the user information based on UID
I want to register each user with their own domain and redirect the functionality to mywww.abc.com/website/home.aspx?UID=1 page.
For example let's say when user type www.user.com user the site will be redirected to mywww.abc.com/website/home.aspx?UID=1 page but the URL of web browser will not change, user can still seewww.user.com on his web browser.
If User click about us link i.e. www.user.com/aboutus/ the site will be redirected towww.abc.com/website/aboutus.aspx?UID=1 page but the URL of web browser will not change.
I have a website say [URL] I am giving the users there own mini site with the [URL] This URL will access to my Home.aspx page located in website folder and display the user information based on UID. I want to register each user with their own domain and redirect the functionality to my [URL] For example let's say when user type [URL] user the site will be redirected to my [URL] page but the URL of web browser will not change, user can still see [URL] on his web browser. If User click about us link i.e. [URL] the site will be redirected to [URL] page but the URL of web browser will not change. I am using IIS 6 and ASP.net 2.0.
I've set up IIS7 on my home computer and have written a very basic ASP.NET website to be deployed on this webserver. Everything works great. How do I determine programmatically the physical path (for instance, "C:inetpub_MyWebsite") of the website? I need to write an XML file to the website's root folder dynamically and therefore need to know the folder's physical location.
I've found myself having a requirement to configure log4net based on a file relative to the physical location of the running ASP.NET web application. We like to start the logger as early as possible, so Application_Start seems a proper place. In IIS6, this works fine and has been running for ages, but now we moved to IIS7 and this won't work anymore:
because the HttpContext.Current is not available in many global.asax (Application, Session) events. This is old news, we all know it raises the now infamous Request is not available in this context error. We don't want to move back to Classic Mode.
Now, the question is simple: without using HttpContext, is it possible to find the physical location of the currently running web application instance?
The url format is somewhat like: [URL] To allow users to visit the login and recovery page, I've added the following entries to my web.config:
[code]....
Is there a form of notation so that I can skip the en-GB part and replace it with a wildcard? I want the login and recovery page etc. to be available regardless of the culture.
Is it possible to have location authorization nodes in a web.config be external?
Such that I could take all of the nodes simlar to
[code]....
And move them outside of the web.config or something simlar? I find these nodes at an extreme amount of noise to a web.config when they're relatively static. Normally my approach would be to config source something like this but since it falls under the root node I'm not sure of it's possible with these nodes.
look at the attached web.config? The last part doesn't seem to work although the path is correct. I've tried logging on the site with a use which is in no groups, but it can still access the page...
I implemented the Location tag in the web.config file to authorize the anonymous users for Images folder. I deployed the code in IIS6.0 with Forms authentication mode enabled for the virtual directory. I disabled all other authentication modes. When I browse the login page, Images are not displaying. When I set Anonymous authentication in IIS6.0 for the Image folder, it works fine.
I am using ASP.NET MVC 3 and am trying to do something that should be really straight forward...
My application uses Forms authentication and that is working perfectly for controllers/actions. For example if I decorate either a controller or an action with the attribute below only members of the administrators group can view them:
[Authorize(Roles="Administrators")]
However I have a folder under the default Scripts folder called Admin. I only want members of the Administrators group to be able to access scripts within this directory so I created a new web.config in the directory with the following inside:
[code]....
However no matter whether a user is a member of the Administrators group or not they receive a 302 Found message and are then redirected to the login page.
If I change the web.config to allow user="*" then it works. It also works if I add an allow users="Username" for a specific user I am testing with.
When a user attempts to directly visit the url admin.aspx, and they are not an admin, they are redirected to the login page. However, the user then attempts to visit ViewWeek.aspx, it indicates that they are still logged in. Why does this ASP.NET authorization boot the user to the login screen, yet keep the user logged in? I'd rather it just direct the user to the default URL specified in the forms tag.
Our team has recently implemented a role permission based authorization so that we can have granular control. This is similar to what Rockford Lhotka suggests herehttp://www.lhotka.net/weblog/PermissionbasedAuthorizationVsRolebasedAuthorization.aspx I have also read about the Claims based authorization which to me looks very similar to what we have. Can some one put in simple terms what the advantages of claims based authorization are.
URL....This link shows a demo that let user to put origin and destination then get direction. I want to know how to add a option which is let user to use their current location as origin location (Location from).
I have a table in my database, in which a certain field holds the locations of text or doc files (the files are of a transcript for a chat session).
In the Gridview right now i able to show the link locations. But i want to have Hyperlink or Button in the links location in the Transcript Location fields.And on the click of which the txt or doc file opens up in notepad or microsoft word.
Following is my code when user enters hospital name and city, he will be navigated to this page to show location on map. Now I want to get user current location and draw the route between current location and destination. Is there any way to integrate to geocoding and geolocation?
Is there a way to get the physical filepath from an ASP.NET's URL?
Scenerio: I have an app that is on two severs, but it will now be on lots more, and each server puts it in a different physical file path. Right now I'm doing this:
//for server 1 if (Request.Url.GetLeftPart(UriPartial.Path).Contains(".com")) { Application["StoreFilesPath"] = "E:\Data\rootsite\f1\appsite\Upload\"; } //for server 2 if (Request.Url.GetLeftPart(UriPartial.Path).Contains(".net")) { Application["StoreFilesPath"] = "E:\Web\rootsite2\f34\abc\ghi\appsite\Upload\"; }
But what I need to do is something like this:
//for all servers Application["StoreFilesPath"] = getPhysicalFilePath() +"\Upload\";
i am trying to insert with bulk and getting the following
Cannot bulk load because the file "D:inetpub.........insertgid.csv" could not be opened. Operating system error code 3(The system cannot find the path specified.).
My basic question is, can a virtual directory in IIS point to a physical path that's not on the local machine? For instance, right now I have a virtual path /NaturalGasReport/NYMEX which points to physical path C:Program Files (x86)NymexSettleNATGAS_REPORTNYMEX, but I want it to point to a physical path on a difference PC on the same network. Is this possible? (I know I can just try it out so I apologize for asking but I thought it would be best to get an explanation along with "yes" or "no"). If you want more detail, this is what I need to do. To make a long story short, because of a vendor product we are using that won't run on a 64-bit operating system, I have to run a program called Generate_NGReportData.vbs (it's a vbscript program) on a PC I will call 28. It uses a vendor product which produces jpg files which are graphs of the Natural Gas market. The machine where I wish it could run is called RTEST01 but this machine runs a 64-bit OS and the components won't work there. RTEST01 has the databases. So, I created a datasource on 28 which points to RTEST01's database. The vbs program will read the data, generate the reports, and write one row to a database table on RTEST01. RTEST01 has to run the complimentary program which sends these reports (via email). 28 is not an email server so it can't email the reports. So on RTEST01 I will run Send_NaturalGasReport.vbs. This program creates an email body of html. The html references [URL]NaturalGasReport/NYMEX/" & Day(nymex_update_dt) & ".jpg which is a virtual directory pointing to C:Program Files (x86)NymexSettleNATGAS_REPORTNYMEX. I need it to point to the folder and files on 28.So if my initial question has a simple yes answer then I am all set. If not, examine my architecture and propose an alternative solution.
How would you accomplish these in ASP.NET Webforms 4.0 Routing;.aspx pages should not be accesible directly, pages should be accesible only with routes, Start page should be "/" or "/home" or something else, but not "Default.aspx".
I use ASP.NET routing to rename the full paths of my URLs (ie. /page1/page2/file.aspx would just become /file.aspx). This doesn't work with web.config authorization, because that uses physical path/folder names.