| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
and other random stuff I noticed.
I think this finishes messing with code style. The codebase should match
the developer style guide closely enough that 99.9% of changes will not
feel the need to also massage the formatting.
|
| |
|
|
|
|
|
|
|
| |
If both `post-check` and `pre-check` are specified and set to `0`, both
are entirely ignored:
http://blogs.msdn.com/b/ieinternals/archive/2009/07/20/using-post_2d00_check-and-pre_2d00_check-cache-directives.aspx
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Sorted by RFC 2616:
Section 14.9.1 `no-cache`
Section 14.9.2 `no-store`
Section 14.9.4 `must-revalidate`
Combined into one line with IE's `pre-check` and `post-check`. However,
when both set to `0`, both are entirely ignored:
http://blogs.msdn.com/b/ieinternals/archive/2009/07/20/using-post_2d00_check-and-pre_2d00_check-cache-directives.aspx
|
| |
|
|
|
|
|
| |
and module names and other bits of formatting and typos in header
comment sections.
|
| |
|
| |
|
|
|
| |
Codeset auto checking pfsense-utils.inc do not need anymore
|
| |
|
| |
|
| |
|
|
|
|
| |
include 2009 on files that I have asserted (C) on
|
|
|
|
| |
this is the same issue as the traffic graph one.
|
|
|
|
|
|
|
|
| |
1) Redefine page privileges to not use static urls
2) Accurate generation of privilege definitions from source
3) Merging the user and group privileges into a single set
4) Allow any privilege to be added to users or groups w/ inheritance
5) Cleaning up the related WebUI pages
|
| |
|
|
|