WordPress.org

Make WordPress Core

Opened 6 years ago

Last modified 3 days ago

#10414 assigned defect (bug)

Some trackbacks timeout due to short timeout period

Reported by: gnaka08 Owned by: chriscct7
Milestone: 4.4 Priority: normal
Severity: normal Version: 2.8
Component: Pings/Trackbacks Keywords: needs-refresh has-patch
Focuses: Cc:

Description

A trackback by WordPress to an external blog can timeout without any network congestion. WordPress 2.8.1 timeouts if it has not received any response from the receiving system for 4 seconds although some blog system can take more than 10 seconds to accept a trackback. If the trackback fails, WordPress keeps trying to resend the trackback every time the user posts a new entry, but it never succeeds and WordPress keeps resending for ever. It annoys the blog owner whose blog the WordPress is trying to send the trackback to.

I propose that function trackback in wp-includes/comment.php should be modified for the timeout period to be extended from 4 seconds (e.g. to 30 seconds).

This modification is different from one appeared in ticket #8665.

Attachments (1)

comment.php.diff (507 bytes) - added by gnaka08 6 years ago.

Download all attachments as: .zip

Change History (8)

@gnaka086 years ago

comment:1 @Denis-de-Bernardy6 years ago

  • Keywords has-patch 2nd-opinion added
  • Milestone changed from Unassigned to 2.9

comment:2 in reply to: ↑ description ; follow-up: @gnaka086 years ago

The timeout in MT4.261 seems to be 60 seconds by default (HTTPTimeout configuration variable). The documentation claims that it is 10 seconds somehow, but lib/MT/Core.pm reads as 60 seconds to me.

http://www.movabletype.org/documentation/appendices/config-directives/httptimeout.html

comment:3 in reply to: ↑ 2 @gnaka086 years ago

Japanese-localized documentation tells that it has been changed to 60 seconds since version 3.3.

http://www.movabletype.jp/documentation/appendices/config-directives/httptimeout.html

comment:4 @janeforshort6 years ago

  • Keywords needs-testing added
  • Milestone changed from 2.9 to Future Release
  • Severity changed from major to normal

Punting due to lack of testing and community traction.

comment:5 follow-up: @jeremyfelt18 months ago

  • Keywords has-patch removed

I think the timeout is working fine here and there is no need to increase the default. One could theoretically use a filter like http_request_args to up the timeout time when necessary. We could also add a filter to the arguments that trackback() pushes to the HTTP request.

Suggesting wontfix for the timeout, though something managing the upper limit of trackback attempts for a URL could be interesting.

comment:6 in reply to: ↑ 5 @gnaka0818 months ago

Since I wrote about this problem on my blog in 2009, some users have reported that they experienced the same problem. They all had felt sorry for the annoyances to owners to whose blog they inadvertently sent many trackbacks. This is a serious issue because it involves a responsibility to others.

comment:7 @chriscct73 days ago

  • Keywords needs-refresh has-patch added; 2nd-opinion needs-testing removed
  • Milestone changed from Future Release to 4.4
  • Owner set to chriscct7
  • Status changed from new to assigned
  • Version changed from 2.8.1 to 2.8

We should match the timeout to 10 seconds

Note: See TracTickets for help on using tickets.