http-status-code-404

I am developing a Django site and after a series of edits I ran my server again when suddenly - no css! The server still displays the html site, of course, but the css all across the site is throwing a 404 error. My static files information in my settings.py wasn't edited at all: import os # hack to accommodate Windows CURRENT_PATH = os.path.abspath(os.path.dirname(__file__).decode('utf-8')).replace('\\', '/') STATIC_URL = '/static/' # Additional locations of static files STATICFILES_DIRS = ( os.path.join(CURRENT_PATH, 'static'), ) My base template does a simple call for the file based on the

I'm a Django developer learning Flask. I'm pretty new to how things work in Flask. I'm getting a 404 with the following code when I visit localhost:5000 . Could someone explain why I'm getting this: The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again. from flask import Flask from flask.ext.sqlalchemy import SQLAlchemy from datetime import datetime app = Flask(__name__) app.config['SQLALCHEMY_DATABASE_URI'] = 'sqlite:////media/workdrive/workspace/purkinje/temp.db' app.debug = True db = SQLAlchemy(app) if __name__ == '__main__':

I'm working with PHP. I have an .htaccess file like below, and it redirects to homepage rather than 404 error page :/ what can be the problem here? Appreciate helps! thanks a lot! ErrorDocument 404 /new/err404.html RewriteEngine On RewriteBase /new/ RewriteRule ^login.html$ index.php?s=login&a=loginDo [QSA,L] RewriteRule ^logout.html$ index.php?s=login&a=logoutDo [QSA,L] RewriteRule ^([^/]*).html$ index.php?s=$1 [QSA,L] RewriteRule ^members/([^/]*)$ index.php?s=profile&username=$1 [QSA,L] RewriteRule ^([^/]*)/$ index.php?s=listing&search[cityString]=$1 [QSA,L] RewriteRule ^([^/]*)/([^/]*)/$

I'm having trouble serving static files in development mode in Django. I do know that this is not a setting that should be used in a production server, so don't worry. For now however I'd like to stick to it. The relevant parts of settings.py are: MEDIA_URL = '/media/' STATIC_URL = '/static/' MEDIA_ROOT = os.path.join(os.path.abspath(os.path.dirname(__file__) + '/..'), 'media') STATIC_ROOT = os.path.join(os.path.abspath(os.path.dirname(__file__) + '/..'), 'static') And of urls.py : urlpatterns += static(settings.MEDIA_URL, document_root=settings.MEDIA_ROOT) urlpatterns += static(settings

All I'm doing is loading mechanize, and getting a page that returns 404. But that's exactly what I want. The 404 page has plenty of html I'd like to use in my example. a = mechanize.new a.get('http://www.youtube.com/watch?v=e4g8jriw4rg') a.page => nil I can't seem to find any further info on this. pguardiario You need to handle the exception: begin page = a.get 'http://www.youtube.com/watch?v=e4g8jriw4rg' rescue Mechanize::ResponseCodeError => e puts e.response_code # the status code as a string, e.g. "404" page = e.page end puts page.title This may have been the case when the answer was

I am unable to let my '404 pages' work using lazy loading modules. When I enter a random url in the browser I only see a blank page instead of my cool 404 page. Here is my routing config export const routes: Routes = [ { path: '', redirectTo: 'dashboard', pathMatch: 'full'}, { path: 'dashboard', loadChildren: 'app/dashboard/dashboard.module#DashboardModule'}, { path: 'buckets', loadChildren: 'app/buckets/buckets.module#BucketsModule'}, { path: '**', loadChildren: 'app/notfound/notfound.module#NotFoundModule'} ]; export const routing: ModuleWithProviders = RouterModule.forRoot(routes); When I

I am trying to create a 404 error page and currently I have all of the following/tried all of the following to try and accomplish this. When the user types in : http://name/something.aspx It works just as its supposed to. But if the user types in: http://name/NotAFile with no .aspx then IIS7 takes matters into its own hands and I get the lovely error page that IIS7 comes with. The goal is that the site redirects with only a 404 status code (so not a 200, or a 302 redirect). I have tried in both the web config with: <customErrors mode="On" defaultRedirect="~/error/Default.aspx redirectMode=

Is there an easier way of getting the content of an HTTP 404 response than directly accessing the host via tcp? This is a sample of a 404 response with content: HTTP/1.1 404 Object Not Found Server: CouchDB/1.3.0 (Erlang OTP/R15B03) Date: Wed, 24 Jul 2013 08:32:50 GMT Content-Type: text/plain; charset=utf-8 Content-Length: 41 Cache-Control: must-revalidate {"error":"not_found","reason":"missing"} The Rebol HTTP scheme really isn't designed with this in mind, it's geared toward reading content the way you would in a browser, not services over HTTP. In saying that, you can hack the protocol to