WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Changes to Pingdom Tools API #4

@xurizaemon

Description

@xurizaemon

Pingdom have modified this (undocumented) API, and it now requires a slightly different interface.

  • If certain criteria are not met, the API response is empty.
  • If other criteria are not met, the API responds with "internal server error"
  • The API endpoint location has changed slightly.
  • The API response format has changed.

Criteria

Based on testing (as of today), the API now requires that:

  • A user-agent header be supplied.
  • A referer header be supplied (and set to https://tools.pingdom.com/?).
  • A callback parameter be passed, see Response below.

Response

The response will now be wrapped in some code for eval():

pingdom_tools && pingdom_tools({"test_id":"abc123","poll_state_url":"https://fpt-api.pingdom.com/api/0.1/test/abc123"});

I'd rather strip or regex that out than pass it to eval(), since otherwise we risk the potential for malicious responses.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions