Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
L
linkchecker-3247797
Manage
Activity
Members
Labels
Plan
Custom issue tracker
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Model registry
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Issue forks
linkchecker-3247797
Commits
ff8ff236
Commit
ff8ff236
authored
11 years ago
by
Alexander Hass
Browse files
Options
Downloads
Patches
Plain Diff
Updated README.txt
parent
94f4e8d5
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.txt
+24
-16
24 additions, 16 deletions
README.txt
with
24 additions
and
16 deletions
README.txt
+
24
−
16
View file @
ff8ff236
...
...
@@ -33,19 +33,27 @@ Required:
Known issues:
1. drupal_http_request() does handle (invalid) non-absolute redirects. The
main issue is a broken webserver configuration and you can try to notify
the site owner about doing non-rfc compliant redirections.
This is a very common administration fault from past days and core should
implement a workaround. See http://drupal.org/node/164365 for more details.
Until this issue is fixed in core the permanently moved links are not
automatically fixed/updated by the "Update permanently moved links" feature
to the newly provided URL.
-> Workaround: Manually fix these links or try the patch.
2. Drupal 6.14 only: A critical core bug has been introduced by #193383:
set_time_limit: Centralize calls and prevent warnings and errors that stops
link checker from verifying links. Apply the available D6 hotfix in #111 or
update to Drupal 6.15+ to fix your installation.
There are a lot of known issues in drupal_http_request(). These have been solved
in HTTPRL. As a workaround it's recommended to use HTTPRL in linkchecker.
Issues list:
* #997648: drupal_http_request() always calls fread() one more time than necessary
* #164365-12: drupal_http_request() does handle (invalid) non-absolute redirects
* #205969-11: drupal_http_request() assumes presence of Reason-Phrase in response Status-Line
* #371495: Error message from drupal_http_request() not UTF8 encoded
* #193073-11: drupal_http_request - socket not initialized
* #106506-8: drupal_http_request() does not handle 'chunked' responses - Make it support HTTP 1.1
* #1096890-15: drupal_http_request should return error if reaches max allowed redirects
* #875342-21: drupal_http_request() should pick up X-Drupal-Assertion-* HTTP headers
* #965078-31: HTTP request checking is unreliable and should be removed in favor of watchdog() calls
* #336367: HTTP client should protect commas when folding (compatibility with legacy HTTP/1.0)
* #45338: log fsockopen errors to watchdog
Other
* Drupal 6.14 only: A critical core bug has been introduced by #193383:
set_time_limit: Centralize calls and prevent warnings and errors that stops
link checker from verifying links. Apply the available D6 hotfix in #111 or
update to Drupal 6.15+ to fix your installation.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment