Hi, There is not much to worry about, they are just best practices, informational or low issues. Except by CSRF but web2py already handle this
- X-Frame-Options Header Not Set (15) Prevent that your site is used under an iframe on another site. Depends of the usage of the app - Cross-Domain JavaScript Source File Inclusion (2) This is optional. Is not mandatory to have all the js in the same app. - Incomplete or No Cache-control and Pragma HTTP Header Set (26) This header prevents the client from caching the response. - Server Leaks Information via "X-Powered-By" HTTP Response Header Field(s) (50) It just discloses "web2py", like every other server header or technology. Is easy to hide if necessary - X-Content-Type-Options Header Missing (48) The HTTP 'X-Content-Type-Options' response header prevents the browser from MIME-sniffing a response away from the declared content-type when. This allows older versions of Internet Explorer and Chrome to perform MIME-sniffing on the response body, potentially causing the response body to be interpreted and displayed as a content type other than the intended content type. - Absence of Anti-CSRF Tokens (13) All forms from web2py have an unique token to prevent this and also double submission. http://web2py.com/books/default/chapter/29/01/introduction#Security Anyway... all of this headers misconfiguration are classified as best practices, informational or low issues. Only csrf could be taken as medium or high issue, but web2py handles this. You can handle the headers at server (apache/nginx) level or at the application level. Cheers! El El jue, 9 de jul. de 2020 a la(s) 09:42, [email protected] < [email protected]> escribió: > Hi, in this days I'm acting pen-test on my web2py application, all tools > used report me that there're some "important" header are missing.. > In particular: > > - X-Frame-Options Header Not Set (15) > - Cross-Domain JavaScript Source File Inclusion (2) > - Incomplete or No Cache-control and Pragma HTTP Header Set (26) > - Server Leaks Information via "X-Powered-By" HTTP Response Header > Field(s) (50) > - X-Content-Type-Options Header Missing (48) > > End also: > > - Absence of Anti-CSRF Tokens (13) > > Where's the mistake? > There's a security Issue??? > > BR > > MS > > -- > Resources: > - http://web2py.com > - http://web2py.com/book (Documentation) > - http://github.com/web2py/web2py (Source code) > - https://code.google.com/p/web2py/issues/list (Report Issues) > --- > You received this message because you are subscribed to the Google Groups > "web2py-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/web2py/55974bec-0b1a-4c30-affe-f3fe2d162d64n%40googlegroups.com > <https://groups.google.com/d/msgid/web2py/55974bec-0b1a-4c30-affe-f3fe2d162d64n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/web2py/CA%2Bs%2BuJub1BLTQo55Tv-YLz7AkCBPvf-o_t2Uws5yHS5Xq-J8uQ%40mail.gmail.com.

