Skip to content
This repository has been archived by the owner on Aug 1, 2019. It is now read-only.

Error adding block to registry #4

Open
elimisteve opened this issue Sep 4, 2013 · 3 comments
Open

Error adding block to registry #4

elimisteve opened this issue Sep 4, 2013 · 3 comments

Comments

@elimisteve
Copy link
Contributor

$ curl -i -X POST -d 'url=https://github.com/elimisteve/block-status-code-retriever' http://registry.webpipes.org/blocksHTTP/1.1 503 Service Unavailable
Content-Type: text/html; charset=utf-8
Date: Wed, 04 Sep 2013 09:40:08 GMT
Server: MochiWeb/1.0 (Any of you quaids got a smint?)
Content-Length: 416
Connection: keep-alive

<!DOCTYPE html>
    <html>
    <head>
      <style type="text/css">
        html, body, iframe { margin: 0; padding: 0; height: 100%; }
        iframe { display: block; width: 100%; border: none; }
      </style>
    <title>Application Error</title></head>
    </head>
    <body>
      <iframe src="//s3.amazonaws.com/heroku_pages/error.html">
        <p>Application Error</p>
      </iframe>                                                                                                                               
    </body>                                                                                                                                   
    </html>
@elimisteve
Copy link
Contributor Author

Heroku is currently experiencing problems, so that could easily be the cause.

@matthewhudson
Copy link
Member

I believe this problem may have occurred because you attempted to add the GitHub project link instead of the actual Block endpoint. This is what you want:

$ curl -i -X POST -d 'url=http://status-code-retriever.herokuapp.com/' http://registry.webpipes.org/blocks

@matthewhudson
Copy link
Member

@elimisteve Regardless, end users should never see the error you encountered (unless Heroku is indeed the problem).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants