I’m building a web app. All the external links worked in my Project directory worked fine before but I noticed that yesterday every time I modify the .css file it didn’t render this change at all. It actually is freezed with the same style regardless if I even erase the whole .css file content.
This is the response that I’m getting when I run flask:
* Running on http://127.0.0.1:5000/ (Press CTRL+C to quit)
* Restarting with stat
* Debugger is active!
* Debugger pin code: 230-950-485
127.0.0.1 - - [09/Mar/2017 17:53:09] "GET / HTTP/1.1" 200 -
127.0.0.1 - - [09/Mar/2017 17:53:10] "GET /static/css/main.css HTTP/1.1" 200 -
127.0.0.1 - - [09/Mar/2017 17:53:10] "GET /static/js/main.js HTTP/1.1" 200 -
127.0.0.1 - - [09/Mar/2017 17:53:10] "GET /static/css/main.css HTTP/1.1" 304 -
127.0.0.1 - - [09/Mar/2017 17:53:14] "GET /favicon.ico HTTP/1.1" 404 -
127.0.0.1 - - [09/Mar/2017 17:54:04] "GET / HTTP/1.1" 200 -
Notice the 304, seems like that might be the problem? I appreciate any advice in what steps to take.
asked Mar 9, 2017 at 23:05
1
In Flask this is very common, whether you use Internal or external files:
HTTP Response
304 NOT MODIFIED
A conditional GET or HEAD request has been received and would have resulted in a 200 OK response if it were not for the fact that the condition evaluated to false.
In other words, there is no need for the server to transfer a representation of the target resource because the request indicates that the client, which made the request conditional, already has a valid representation; the server is therefore redirecting the client to make use of that stored representation as if it were the payload of a 200 OK response.
This means Flask is telling the browser that it already has the content.
If you clear your browser cache and you will notice that Flask returns a 200 on your next request.
answered Jan 11, 2018 at 10:24
Disabling cash solutions for this issue is not working for me.
If it doesn’t update the file because it already represented, it means if i have new code in my file, i will never be able to push these modifications
answered Nov 8, 2020 at 9:51
SystemXSystemX
4714 silver badges10 bronze badges
1
304 means you have compiled that file before and there are no modifications to the file. You can clear them by deleting cache file on pycache folder
answered Apr 8 at 2:20
Flask API includes a set of named constants that you can use to make more code more obvious and readable.
from flask_api import status
...
@app.route('/empty-view/')
def empty_view(self):
content = {'please move along': 'nothing to see here'}
return content, status.HTTP_404_NOT_FOUND
The full set of HTTP status codes included in the status module is listed below.
The module also includes a set of helper functions for testing if a status code is in a given range.
from flask_api import status
import unittest
...
class ExampleTestCase(unittest.TestCase):
def test_success(self):
with app.test_client() as client:
response = client.get('/')
self.assertTrue(status.is_success(response.status_code))
For more information on proper usage of HTTP status codes see RFC 2616
and RFC 6585.
Informational — 1xx
This class of status code indicates a provisional response. There are no 1xx status codes used in REST framework by default.
HTTP_100_CONTINUE
HTTP_101_SWITCHING_PROTOCOLS
Successful — 2xx
This class of status code indicates that the client’s request was successfully received, understood, and accepted.
HTTP_200_OK
HTTP_201_CREATED
HTTP_202_ACCEPTED
HTTP_203_NON_AUTHORITATIVE_INFORMATION
HTTP_204_NO_CONTENT
HTTP_205_RESET_CONTENT
HTTP_206_PARTIAL_CONTENT
Redirection — 3xx
This class of status code indicates that further action needs to be taken by the user agent in order to fulfill the request.
HTTP_300_MULTIPLE_CHOICES
HTTP_301_MOVED_PERMANENTLY
HTTP_302_FOUND
HTTP_303_SEE_OTHER
HTTP_304_NOT_MODIFIED
HTTP_305_USE_PROXY
HTTP_306_RESERVED
HTTP_307_TEMPORARY_REDIRECT
Client Error — 4xx
The 4xx class of status code is intended for cases in which the client seems to have erred. Except when responding to a HEAD request, the server SHOULD include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition.
HTTP_400_BAD_REQUEST
HTTP_401_UNAUTHORIZED
HTTP_402_PAYMENT_REQUIRED
HTTP_403_FORBIDDEN
HTTP_404_NOT_FOUND
HTTP_405_METHOD_NOT_ALLOWED
HTTP_406_NOT_ACCEPTABLE
HTTP_407_PROXY_AUTHENTICATION_REQUIRED
HTTP_408_REQUEST_TIMEOUT
HTTP_409_CONFLICT
HTTP_410_GONE
HTTP_411_LENGTH_REQUIRED
HTTP_412_PRECONDITION_FAILED
HTTP_413_REQUEST_ENTITY_TOO_LARGE
HTTP_414_REQUEST_URI_TOO_LONG
HTTP_415_UNSUPPORTED_MEDIA_TYPE
HTTP_416_REQUESTED_RANGE_NOT_SATISFIABLE
HTTP_417_EXPECTATION_FAILED
HTTP_428_PRECONDITION_REQUIRED
HTTP_429_TOO_MANY_REQUESTS
HTTP_431_REQUEST_HEADER_FIELDS_TOO_LARGE
Server Error — 5xx
Response status codes beginning with the digit «5» indicate cases in which the server is aware that it has erred or is incapable of performing the request. Except when responding to a HEAD request, the server SHOULD include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition.
HTTP_500_INTERNAL_SERVER_ERROR
HTTP_501_NOT_IMPLEMENTED
HTTP_502_BAD_GATEWAY
HTTP_503_SERVICE_UNAVAILABLE
HTTP_504_GATEWAY_TIMEOUT
HTTP_505_HTTP_VERSION_NOT_SUPPORTED
HTTP_511_NETWORK_AUTHENTICATION_REQUIRED
Helper functions
The following helper functions are available for identifying the category of the response code.
is_informational() # 1xx
is_success() # 2xx
is_redirect() # 3xx
is_client_error() # 4xx
is_server_error() # 5xx
Flask API includes a set of named constants that you can use to make more code more obvious and readable.
from flask_api import status
...
@app.route('/empty-view/')
def empty_view(self):
content = {'please move along': 'nothing to see here'}
return content, status.HTTP_404_NOT_FOUND
The full set of HTTP status codes included in the status module is listed below.
The module also includes a set of helper functions for testing if a status code is in a given range.
from flask_api import status
import unittest
...
class ExampleTestCase(unittest.TestCase):
def test_success(self):
with app.test_client() as client:
response = client.get('/')
self.assertTrue(status.is_success(response.status_code))
For more information on proper usage of HTTP status codes see RFC 2616
and RFC 6585.
Informational — 1xx
This class of status code indicates a provisional response. There are no 1xx status codes used in REST framework by default.
HTTP_100_CONTINUE
HTTP_101_SWITCHING_PROTOCOLS
Successful — 2xx
This class of status code indicates that the client’s request was successfully received, understood, and accepted.
HTTP_200_OK
HTTP_201_CREATED
HTTP_202_ACCEPTED
HTTP_203_NON_AUTHORITATIVE_INFORMATION
HTTP_204_NO_CONTENT
HTTP_205_RESET_CONTENT
HTTP_206_PARTIAL_CONTENT
Redirection — 3xx
This class of status code indicates that further action needs to be taken by the user agent in order to fulfill the request.
HTTP_300_MULTIPLE_CHOICES
HTTP_301_MOVED_PERMANENTLY
HTTP_302_FOUND
HTTP_303_SEE_OTHER
HTTP_304_NOT_MODIFIED
HTTP_305_USE_PROXY
HTTP_306_RESERVED
HTTP_307_TEMPORARY_REDIRECT
Client Error — 4xx
The 4xx class of status code is intended for cases in which the client seems to have erred. Except when responding to a HEAD request, the server SHOULD include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition.
HTTP_400_BAD_REQUEST
HTTP_401_UNAUTHORIZED
HTTP_402_PAYMENT_REQUIRED
HTTP_403_FORBIDDEN
HTTP_404_NOT_FOUND
HTTP_405_METHOD_NOT_ALLOWED
HTTP_406_NOT_ACCEPTABLE
HTTP_407_PROXY_AUTHENTICATION_REQUIRED
HTTP_408_REQUEST_TIMEOUT
HTTP_409_CONFLICT
HTTP_410_GONE
HTTP_411_LENGTH_REQUIRED
HTTP_412_PRECONDITION_FAILED
HTTP_413_REQUEST_ENTITY_TOO_LARGE
HTTP_414_REQUEST_URI_TOO_LONG
HTTP_415_UNSUPPORTED_MEDIA_TYPE
HTTP_416_REQUESTED_RANGE_NOT_SATISFIABLE
HTTP_417_EXPECTATION_FAILED
HTTP_428_PRECONDITION_REQUIRED
HTTP_429_TOO_MANY_REQUESTS
HTTP_431_REQUEST_HEADER_FIELDS_TOO_LARGE
Server Error — 5xx
Response status codes beginning with the digit «5» indicate cases in which the server is aware that it has erred or is incapable of performing the request. Except when responding to a HEAD request, the server SHOULD include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition.
HTTP_500_INTERNAL_SERVER_ERROR
HTTP_501_NOT_IMPLEMENTED
HTTP_502_BAD_GATEWAY
HTTP_503_SERVICE_UNAVAILABLE
HTTP_504_GATEWAY_TIMEOUT
HTTP_505_HTTP_VERSION_NOT_SUPPORTED
HTTP_511_NETWORK_AUTHENTICATION_REQUIRED
Helper functions
The following helper functions are available for identifying the category of the response code.
is_informational() # 1xx
is_success() # 2xx
is_redirect() # 3xx
is_client_error() # 4xx
is_server_error() # 5xx
I’m working with flask and I do not get the view for my web page. Flask server return me that
127.0.0.1 - - [17/Feb/2018 15:26:09] "GET / HTTP/1.1" 200 -
127.0.0.1 - - [17/Feb/2018 15:26:09] "GET /static/vendor/bootstrap/css/bootstrap.min.css HTTP/1.1" 304 -
127.0.0.1 - - [17/Feb/2018 15:26:09] "GET /static/vendor/font-awesome/css/font-awesome.min.css HTTP/1.1" 304 -
127.0.0.1 - - [17/Feb/2018 15:26:09] "GET /static/vendor/magnific-popup/magnific-popup.css HTTP/1.1" 304 -
127.0.0.1 - - [17/Feb/2018 15:26:09] "GET /static/css/creative.min.css HTTP/1.1" 304 -
127.0.0.1 - - [17/Feb/2018 15:26:09] "GET /favicon.ico HTTP/1.1" 404 -
my _nav.html. the links to the css and js files are there.
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<link href="{{url_for('static', filename='vendor/bootstrap/css/bootstrap.min.css')}}" rel="stylesheet">
<link href="{{url_for('static', filename='vendor/font-awesome/css/font-awesome.min.css')}}" rel="stylesheet" type="text/css">
<link href="{{url_for('static', filename='vendor/magnific-popup/magnific-popup.css')}}" rel="stylesheet">
<link href="{{url_for('static', filename='css/creative.min.css')}}" rel="stylesheet">
<title>Title</title>
</head>
<body id="page-top">
<nav id="mainNav" class="navbar navbar-default navbar-fixed-top">
<div class="container-fluid">
<!-- Brand and toggle get grouped for better mobile display -->
<div class="navbar-header">
<button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#bs-example-navbar-collapse-1">
<span class="sr-only">Toggle navigation</span> Menu <i class="fa fa-bars"></i>
</button>
<a class="navbar-brand page-scroll" href="#page-top">Start Bootstrap</a>
</div>
<!-- Collect the nav links, forms, and other content for toggling -->
<div class="collapse navbar-collapse" id="bs-example-navbar-collapse-1">
<ul class="nav navbar-nav navbar-right">
<li>
<a class="page-scroll" href="#about">About</a>
</li>
<li>
<a class="page-scroll" href="#services">Services</a>
</li>
<li>
<a class="page-scroll" href="#portfolio">Portfolio</a>
</li>
<li>
<a class="page-scroll" href="#contact">Contact</a>
</li>
</ul>
</div>
<!-- /.navbar-collapse -->
</div>
<!-- /.container-fluid -->
</nav>
</body>
</html>
I do not get anything like view in my browser
NB : It’s a bootstrap template
Issue
I am having an issue with a flask app that I can’t seem to track down.
The first time I load the index page of my flask app, all resources load correctly. If I reload the page, I get 304 errors on some resources that are loaded from my static directory. These resources have not changed, so the 304 is correct, but it seems like there is not a local resource in the cache.
As you can see in the developer console of chrome, the resources that are red, are ones that have 304’d, and if I click on one of them to view their contents it appears as though no cached version of the resource exists:
No data found from cached resource
This breaks the functionality of the page. If I hard reload, or clear cache and hard reload, the resources load just fine. Also if I just disable cache in chrome, then the page always loads fine, but this requires the developer console to always be open. This flask app did not always do this. Something with flask or chrome has changed since when it was written and I cannot figure it out.
I have also tried tricks like others have recommended with putting date modified tags onto the url, but this doesn’t change the outcome. It seems like the local cache of chrome is broken.
This also happens in Microsoft Edge and Firefox.
What is happening!!! This is driving me mad!!!
Solution
Try downgrading the version of both Flask and Werkzeug (v2.0.2 worked for me).
I was using version 2.1.1 and I was having the same issue, but I had another app that used those two libraries that was not failing, and it was using version 2.0.2 of both of them.
Downgrading did the trick for me.
Hope it helps!
Answered By – fermartinez
This Answer collected from stackoverflow, is licensed under cc by-sa 2.5 , cc by-sa 3.0 and cc by-sa 4.0