http-status-code-404

404 vs 403 when directory index is missing

删除回忆录丶 提交于 2019-12-03 13:11:59
This is mostly a philosophical question about the best way to interpret the HTTP spec. Should a directory with no directory index (e.g. index.html) return 404 or 403? (403 is the default in Apache.) For example, suppose the following URLs exist and are accessible: http://example.com/files/file_1/ http://example.com/files/file_2/ But there's nothing at: http://example.com/files/ (Assume we're using 301s to force trailing slashes for all URLs.) I think several things should be taken into account: By default, Apache returns 403 in this scenario. That's significant to me. They've thought about

Wordpress 403/404 Errors: You don't have permission to access /wp-admin/themes.php on this server

久未见 提交于 2019-12-03 13:08:10
问题 Some background: I setup six blogs this week, all using Wordpress 2.92, installed with Fantastico on a baby croc plan with Hostgator. I used the same theme (heatmap 2.5.4) and plugins for each blog. They were all up and running, no issues at all. I go to create a new blog this morning, using the same setup, and when I try to change the theme settings, I get the following error: Forbidden You don't have permission to access /wp-admin/themes.php on this server. Additionally, a 404 Not Found

React nested route fails to load on refresh

这一生的挚爱 提交于 2019-12-03 13:05:44
问题 I have a React app with navigation powered by react-router that I run in development with webpack-dev-server and the history fallback option enabled. Here is the routes I have defined in my index.js ReactDOM.render(( <Router history={browserHistory}> <Route path="/" component={App}> <IndexRedirect to="/intro" /> <Route path="/intro" component={Intro} /> <Route path="/device" component={Device} /> <Route path="/clothing" component={Clothing} /> <Route path="/build" component={Build}>

Express status 404 with react-router

泄露秘密 提交于 2019-12-03 12:52:52
I have an express server that handles: 1 API route and rendering my initial index.html to include bundle.js holding my React/React-Router/Redux application. As it stands, it is impossible to 404 on my web page as I have a catch all: app.use(function (req, res) { return res.render('index') }) In order for react-router 's NoMatch to work I need to send a 404 code. My routes are as follows: Express — /api/test/:x/:y React Router — :x/ , :x/:y What I am essentially trying to achieve is, if the user ever goes to a URL of: :x/:y/z/and/further then return a 404, unless what they've gone to is /api

Google App Engine Static Files GET 404

自古美人都是妖i 提交于 2019-12-03 12:41:20
The following app.yaml works great on my local dev server.. but when I deploy it to production all static files throw 404. Server isn't able to locate any static files. Have been searching for hours couldn't find a valid solution. Note: I am developing with mac, so aware of the case sensitive nature of the system. application: dev-scanner version: 1 runtime: python api_version: 1 handlers: - url: /(.+) static_files: static_files/\1 upload: ./static_files/(.+) - url: / static_files: static_files/index.html upload: ./static_files/index.html Here is the error from the log 2011-03-18 01:18:07.033

web.config errors fail with responseMode=“File”

我怕爱的太早我们不能终老 提交于 2019-12-03 12:06:10
According to Microsoft's documentation , for static (i.e. HTML) content, web.config should read responseMode="File" for each error. Currently, my web.config includes <httpErrors errorMode="Custom"> <!-- remove statusCodes --> <error statusCode="404" path="/error/404.html" responseMode="ExecuteURL" /> </httpErrors> This returns the correct custom error page, but returns a 200 OK status code. When I change "ExecuteURL" to "File", my server does return a 404, but the custom error page is not displayed. Instead, I get the message "The resource you are looking for has been removed, had its name

MVC 4 - LogOff controller action giving 404 not found

与世无争的帅哥 提交于 2019-12-03 10:34:31
I'm just wrapping up a college project, I'm not sure if I've been staring at my computer for too long and am missing something obvious, but when I try to log a user out, I'm getting a 404 not found for the URL /Account/LogOff. I have a navbar that shows Log in/Log out depending on whether a user is, logged in, or, logged out: <div class="nav-collapse collapse"> <ul class="nav pull-right"> <li class="dropdown" id="dropdown-login-div"> @if (!Request.IsAuthenticated) { <a class="dropdown-toggle" href="#" data-toggle="dropdown">Sign In <strong class="caret"></strong></a> } else { @Html.ActionLink(

Coldfusion 10, IIS 7.5 - Getting a 404 even though file exists

故事扮演 提交于 2019-12-03 09:51:13
I'm getting a 404 even though the page exists on disk. I've ran the Web Server Configuration Tool and rebooted several times. Handler mapping for .cfm files (configuration tool seems to have worked): C:\ColdFusion10\config\wsconfig\1\isapi_redirect.dll Virtual Paths: root/index.cfm <- works root/dan.cfm <- doesn't work Server: Windows 2008 R2, IIS 7.5 and Coldfusion 10 Rest of my configuration: Update 1 NTFS Security Information on /wsconfig/1 folder: Answer - TLDR Map a virtual directory named "jakarta" to CFUSION INSTALL\config\wsconfig{instance id} No need to add APPPool permissions to

Visual Studio 2012 Web Deploy to Windows Server 2008 R2 with IIS 7 and /msdeploy.axd 404 error

旧街凉风 提交于 2019-12-03 09:44:31
In Visual Studio 2012 RC when I try to validate a Web Deploy connection I get this error message: ERROR_DESTINATION_NOT_REACHABLE The required Web Management Service is started on the server and Web Deploy 3.0 RC is installed. Then using Remote Desktop Connection I log on the server and go check IIS logs located at C:\inetpub\logs\LogFiles\W3SVC1 . There I can see my attempts to validate the connection because they contain my IP address: 2012-07-13 20:58:49 185.201.117.17 HEAD /msdeploy.axd site=Default%20Web%20Site 8172 - 189.10.32.194 - 404 0 2 78 It's giving me a 404. After trying to get

Send a 404 error via htaccess?

孤人 提交于 2019-12-03 09:33:28
I'd like to cut off access to a subdirectory on my site but I want any access in the subdirectory to be a 404 error, not a 403 forbidden. How can this be accomplished? Try: RewriteRule ^directory/ - [L,R=404] This redirects all requests for the folder " /directory/ ", they get a 404 response. You could also for the time being change which page a user will see when confronted with a 403 error, but I wouldn't recommend doing this long-term. .htaccess: ErrorDocument 403 /your404pagehere.php I think, 410 error better RewriteRule ^directory/ - [L,R=410] or my search: RewriteCond %{HTTP_USER_AGENT}