Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
This fixes two bugs:
- for segments that ends with ".." e.g. /user/username../details, this should not be replaced
- current solution only replace double slashes, this solutions removes the infinite number of recurring slashes
|
|
|
|
config->site_url() optimizations
|
|
thanks to narfbg
|
|
- direct access to config array, instead of item() calls
- the string cast is just in case 'url_suffix' would be set to false or null; the function produces the same results without this cast, but it leads to a robuster code, as false and null are sanitized and skip the suffix insertion code
- altered conditional structure: if no suffix, skip the appending of an empty string to $uri
|
|
(an improved version of PR #609)
|
|
(an improved version of PR #645)
Also fixed get_content_type() to only return the MIME value and created
Output library unit tests for both of these methods.
|
|
|
|
(as requested in issue #452)
|
|
Signed-off-by: dchill42 <dchill42@gmail.com>
|
|
|
|
not specified
|
|
|
|
|
|
It is a core class after all, I guess somebody forgot it when the rest of them were moved.
|
|
|
|
|
|
|
|
It is now used to check whether dangerous functions like eval() and exec() are available.
It appears that the Suhosin extension (which is becoming popular) terminates script
execution instead of returning e.g. FALSE when it has a function blacklisted.
function_exists() checks are insufficient and our only option is to check the ini
settings here.
Filed an issue here: https://github.com/stefanesser/suhosin/issues/18
... hopefully we'll be able to deal with this in a more elegant way in the future.
(this commit supersedes PR #1809)
|
|
Helps in reading php://input stream data by caching it when accessed for the first time.
(supersedes PR #1684)
|
|
Also, their property is no longer public and the utility class no longer extends CI_DB_forge.
|
|
- PDO subdrivers are isolated from each other now.
- Added compatibility for pretty much all of the features, for every DB platform.
- Unified the way that stuff works in general.
- Fixes issue #1005.
|
|
Seems to be causing issues (see #1970).
Also updated the Controller docs, mainly to include an important note related to #1967.
|
|
Fix / Disallowed Key Characters.
|
|
|
|
It appears to break get_instance()->*_package_path*() usage which is very common.
Need to figure out how to resolve this.
|
|
That method used to be called by the CI_Controller constructor
and was required because of the possibility to instantiate the
Controller class twice due to 404_override, and so some properties
needed to be reset.
Following the last commit - this is no longer the case.
|
|
- Don't instantiate the CI singleton twice.
- General clean-up.
- Fix issue #953.
|
|
|
|
|
|
|
|
An improved version of changes suggesed in PR #1352, and more specifically:
https://github.com/sourcejedi/CodeIgniter/commit/8f7d2dfe42bd8543981c0f295e391e433d82fd42
https://github.com/sourcejedi/CodeIgniter/commit/d2de251c092d9d822fc4898e3681b64e9c74dd2a
(thanks again @sourcejedi)
|
|
|
|
Supersedes PR #642
|
|
Also partially fixes issue #1295, fixes inconsistencies in some page-level docblocks and adds include checks in language files.
|
|
(thanks to @sourcejedi, PR #1326)
Up until PHP 5.2.4 (which is our new lowest requirement),
there was a bug related to PATH_INFO which made REQUEST_URI
a more reliable choice. This is now no longer the case,
see https://bugs.php.net/bug.php?id=31892 for more details.
Also removed ORIG_PATH_INFO from the suggested alternatives
for uri_protocol in application/config/config.php as it will
not exist in most of PHP's recent versions and is pointless
when you can use PATH_INFO anyway.
|
|
f2b19fee7876708c7a7bb5cba6b7df682a9d2a53
|
|
(thanks to @sourcejedi, PR #1326 for pointing inconsistencies with RFC2616
|
|
Processed routes
|
|
|
|
|
|
(thanks to @sourcejedi, PR #1326 for most of the ideas)
- Renamed _detect_uri() and _parse_cli_args() to _parse_request_uri() and _parse_argv() respectively.
- Added _parse_query_string() which allows us to detect the URI path from QUERY_STRING much like it is done in _parse_request_uri().
(the above changes also allow for a simpler logic in the case where the *uri_protocol* setting is not set to 'AUTO')
- Updated application/config/config.php with a better list of the *uri_protocol* options.
- Added _reset_query_string() to aid in re-processing from the QUERY_STRING (utilized in _parse_request_uri() and _parse_query_string()).
|
|
(thanks to @sourcejedi, PR #1326)
For HTTP/1.1 compliance, RFC2616 specifies that both relative
and absolute URI formats must be accepted:
- http://localhost/path/ (absolute)
- /path/ (relative)
|
|
|
|
|
|
|
|
|