Project

General

Profile

Actions

Bug #51172

closed

Strange Linkvalidator Reports

Added by Henrik Ziegenhain over 10 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Linkvalidator
Target version:
-
Start date:
2013-08-19
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.1
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

It seems, the Linkvalidator is not correct checking and reporting the broken links.
Or he is drunk, I donĀ“t know :)

Here are some reports from the last days.
Please have a look at the number of broken links - nothing on the site changed.
The real amount of total broken links should be 5 (this is not correct checked by the validator, but that`s another issue)

1. August:
Total broken links: 53 (last report: 52)
Page: root
All links types: 53 (last report: 52)
Internal link: 49 (last report: 49)
External link: 4 (last report: 3)

2. August:
Total broken links: 5 (last report: 53)
Page: root
All links types: 5 (last report: 53)
Internal link: 2 (last report: 49)
External link: 3 (last report: 4)

3. August:
Total broken links: 7 (last report: 5)
Page: root
All links types: 7 (last report: 5)
Internal link: 2 (last report: 2)
External link: 5 (last report: 3)

4. August:
Total broken links: 8 (last report: 7)
Page: root
All links types: 8 (last report: 7)
Internal link: 2 (last report: 2)
External link: 6 (last report: 5)

5. August:
Total broken links: 5 (last report: 8)
Page: root
All links types: 5 (last report: 8)
Internal link: 2 (last report: 2)
External link: 3 (last report: 6)

This phenomenon occurs on different installations (6.1 and 4.7 also).

Actions #1

Updated by Philipp Gampe over 10 years ago

  • Status changed from New to Needs Feedback

On 6.1, the internal link check will detect FAL file links as brocken internal links. I suggest to not use the internal link checker, because it does not work reliable anyway.

This should not happen on 4.7, though.

The number of external fails can very, depending on the network connection, availability of the external targets, etc.

It would be interesting to know what kind of errors are reported on the days with many link errors.

Actions #2

Updated by Henrik Ziegenhain over 10 years ago

Oh... The affected Installation is running on 6.0 instead of 6.1.

Never the less: Today there are only 8 reported errors:

1: http://www.bundesverband-erlebnispaedagogik.de/be/pages/start/fachbereiche/klassenfahrten-und-gruppenprogramme/guetesiegel-beq--mit-sicherheit-paedagogisch.php
   Ausnahme: Curl error: Empty reply from server

2: http://www.partyservice-bischoff.de
   Ausnahme: Curl error: connect() timed out!

3: http://www.oeffentliche.de/web/html/privat/versicherungen-vam/index.html?reiter=1
   Interner Serverfehler (500)

4: http://www.uwekind.com/de/
   Ausnahme: DateTime::__construct(): Failed to parse time string (0m) at position 0 (0): Unexpected character

1-3 maybe could really be a temporary issue - I will check this tomorrow.
4 is there everyday.

As far as I coult overview, there are no FAL file links detected as broken (on 6.0!).

When the Validator reports many more links I will update this issue.

Actions #3

Updated by Philipp Gampe over 10 years ago

4. is a problem of the remote side. 0m is not a valid value for cookie|expires.

1.-3. look like errors of the remote side too. Not all remotes allow all user agents. Sometimes, sites are just down or overloaded.

Actions #4

Updated by Michael Stucki over 10 years ago

  • Category set to Linkvalidator
Actions #5

Updated by Michael Stucki over 10 years ago

  • Project changed from 1510 to TYPO3 Core
  • Category changed from Linkvalidator to Linkvalidator
Actions #6

Updated by Alexander Opitz about 10 years ago

  • Is Regression set to No

Hi,

can we close this issue, as it seams no issue on the side of Linkvalidator.

Actions #7

Updated by Alexander Opitz over 9 years ago

  • Status changed from Needs Feedback to Closed

No feedback within the last 90 days => closing this issue.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions

Also available in: Atom PDF