Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author John Godley

    (@johnny5)

    I don’t know what might be causing it, but you can look at the referrer, user agent, and IP information to see where the requests are coming from. You may have something misconfigured that is causing bad requests to be made.

    Thread Starter mygcdev

    (@mygcdev)

    Thanks John. Yeah I’m a bit baffled by this and not sure what else to do.

    Here is one of the referrer details:

    Agent Mozilla/5.0 (Linux; Android 6.0.1; CPH1701 Build/MMB29M; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/69.0.3497.100 Mobile Safari/537.36 [FB_IAB/FB4A;FBAV/192.0.0.34.85;]
    Device Facebook
    Operating System Android 6.0.1
    Browser Facebook 192.0.0.34.85
    Engine WebKit 537.36

    Plugin Author John Godley

    (@johnny5)

    So it seems like something from Facebook, or the Facebook app? The next version of Redirection will provide better tools for investigating 404s, so that may help

    Thread Starter mygcdev

    (@mygcdev)

    Thanks John. Just an update on this, about a week after I posted this here, the 404 errors that had all these twitter call backs just stopped one day. My sys admin is thinking it may have been something to with an updated security part of the twitter API. Still unsure, but at least they have stopped, I had over 43,000 in the logs 🙁

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘404 – Twitter Embed’ is closed to new replies.