I have setup my website (ASP.NET 4.0) with AJAX, running with no problems at all.
When I test my website locally and on my main top level domain, there are no problems.
When I'm on a subdomain page, AJAX client side framework fails to load. I observed the problem deeply and found that whenever I'm on a subdomain page, WebResource.axd DOES load but ScriptResource.axd DOESN'T load (returns 404 Not Found error). I think I should modify some entries at web.config file, but I have no idea on what to do?
If you want to see the problem live, go to www.123tiendas.com/subdominios/articulo/default.aspx?id=2020 and there's no problem. Go to www.articulo.123tiendas.com/?id=2020 and you'll see the problem. (use any web developer tools to see what is returned)
GET http://articulo.123tiendas.com/ScriptResource.axd?d=BHVdt7ZKRNgWkcmIzZPX-cQ…NHSxpLPXcqbJyg46pdNsVlEnaL_JpR-IQ0IdhPXwT575CanbqzCN8vtDLDFF9A2&t=48e38e19 404 (Not Found) articulo.123tiendas.com:119
Related
On our websites as someone visits a non-existing page, we dinamically create a 404 error page that returns a status code 404.
It works perfectly on localhost, but on the server the same page returns the standard 404 IIS (7.0) error
(IISError) instead of the custom one CustomError.
We can't edit the web.config file because we don't have a physical page to redirect to.
Is it possible that there is a IIS configuration that prevents our custom error page from showing?
There is a configuration setting in IIS. Click your application in IIS, and find Error pages settings.
For the error code, you could specify location of your custom page.
I've just opened a Web Site project found on my predecessor's machine and - I hate the things and don't ever work with them - I get a 404 on every link I click, while the page is definitely present. If I directly view the individual page in the browser, that page works fine, except for any links on it to other pages.
It's like the built-in dev web server isn't operating and interpreting URL requests, but I have no idea where to look to clear this up.
USING IIS: If I create and deploy this site under IIS, everything seems to work normally.
MY MAIN QUESTION IS: Why do pages get not get served on this site and do get served on similar sites, under debugging a Web Site project on VS2012. It is not how to solve the problem by deploying to IIS.
I am in the process of migrating an ASP.net to an HTML website. This is new to me as I only usually do designs for websites.
The URL is the same and so are all the file names (apart from the extensions, of course). I have no clue on ASP.net websites which is where I am getting stuck. I am running the site on a Windows Server and would like to be able to re-direct all the .aspx files to the corresponding .html files
I have read up about .htaccess but have had no luck, I think I need to be running Apache?
Does anybody have any idea how I can solve this? There are similar questions on here but the answers aren't dumbed down enough for me!
Also, when i try the htaccess option I get this error:
Server Error in '/' Application. The resource cannot be found. Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly. Requested URL: /about-us.aspx
KISS solution: If there are only a few number of pages and there really is no logic in the .aspx pages, you could always just load all of the possible web pages, and save them as .html pages via the browser functionality. Google Chrome allows you to right-click on each page and choose Save as... Internet Explorer & Firefox have similar functionality. These pages that you save can then be uploaded to your Go-Daddy site.
So here's the issue. We run Sitecore, which does URL rewriting, and allows for something like example.com/Folder/Page.aspx to be a proper URL.
Now, "Folder" doesn't actually exist on the file system, and neither does "Page.aspx". But those URL's work, because ASP.NET does what it's supposed to.
Okay, so now say I try to go to a web page that doesn't exist like example.com/idontexist.html. This doesn't exist in on the file system, and doesn't use ASP.NET to resolve the file, so then we get a IIS7 404 Error.
Now, I want to change the 404 Error Page to a Custom Error Page, by using a URL. Say, the URL is example.com/ErrorPage.aspx. This page is actually, not a physical page, but an item in Sitecore.
In the Custom Error configuration in IIS Manager, I am trying to change the 404 Error to point to a "URL Redirect" and I'm using "/ErrorPage.aspx" as the URL redirect. When I try to then go to a URL that doesn't exist, IIS7 blows up with an error saying that it can't find /ErrorPage.aspx.
In IIS6, this isn't an issue, and everything works fine. But on IIS7, I redirect to a URL that isn't physically on the server.
Help!
to make a very long story short, here's the thing:
1) configure IIS so that 404 errors go to "default.aspx"
2) create a page that actually handles what you want to handle.
Reference links, SDN originals:
http://sdn5.sitecore.net/upload/sitecore6/handling_http_404_a4.pdf
http://sdn.sitecore.net/upload/sitecore6/dynamic_links_a4.pdf
I am using Sitecore as a CMS solution. Recently, we decided to add redirect capability to our website for errors. In Sitecore, I have created two content pages, one to handle Server errors and another to handle 404 errors. I implemented the server error with basic sublayouts without any code behind. On the other hand, the 404 page had a sublayout that allows to display the link that was typed that resulted to the 404 error. I then proceeded to add these pages into the web.config file (I edited the customErrors setting to redirect to the Server errors page and the 404 errors to redirect to the 404 error page. I also replaced the NoItems settings to point to my 404 error page.
In addition, I changed the HTTP Error 404 to point to my new 404 error page in IIS (5.1). Lo and behold, my changes worked; I was able to redirect many of the errors to these new pages. However, what I found out is that by forcing IIS to redirect to my aspx page for 404 errors, My website now features extensionless URL redirecting. (Previosly if I typed http://mywebsite/foo, I will get a 404 error. Now after doing all of this, it gets me to the foo.aspx page)
Can anyone explain this behavior? Any plausible explanation will let me sleep at night.
Should I go ahead and use this as a temporary solution for Extensionless URL redirecting? What could be wrong with this solution?
Look for this in the web.config in the linkManager section:
addAspxExtension
Is that set to true? If so, then this is a sitecore setting you would have to change.