New short URL with bookmarklet or http/REST request

Implementing this is not a problem, at all. The key is to come up with a workflow that is both user-friendly and secure.

Bit.ly does not put much security on new URL creation (at least nothing obvious, there may be too-many-from-same-IP protection), which raises concerns about DDOS attacks?

This feature would be much appreciated. It's hard to use this module without a bookmarklet.

In my opinion, throttling requests and preventing abuse is way beyond the scope of this module. Drupal already has access rules and CAPTCHA modules and Drupal administrators can employ other techniques as well, like server-side logging and soft bans.

I wrote an implementation for my own usage. The patch attached provides a REST API method which is very similar to the shorten API method from bit.ly, documented here:

http://code.google.com/p/bitly-api/wiki/ApiDocumentation#/v3/shorten

My implementation runs on /v1/shorten and requires the arguments:

username: username of Drupal account
password: password (plaintext)
uri: long url to be shortened
format: "json", "xml" or "txt" (optional, defaults to "json")

The response codes can be:

500: Missing username/password/uri argument
500: Invalid URI
401: Invalid credentials
403: Permission denied
200: OK

In case of 200, the respones includes the "url" and "long_url" fields.

The username and password are checked against the Drupal users. The Drupal user must have the "use shorturl" permission (this permission is new, since shorturl doesn't use permissions yet).

You can only use the GET method now. Drupal clears the values in $_POST, making the implementation for POST a bit difficult.

After applying this patch (and running update.php to force menu rebuild) you may try the following examples:

/v1/shorten?username=USERNAME&password=PASSWORD&uri=http://example.com/

{ "status_code": 200, "status_txt": "OK", "data": { "url": "http://short/lqC", "long_url": "http://example.com/" } }

/v1/shorten?username=USERNAME&password=PASSWORD&uri=http://example.com/&format=xml

<response>
  <status_code>200</status_code>
  <status_txt>OK</status_txt>
  <data>
    <url>http://short/lqC</url>
    <long_url>http://example.com/</long_url>
  </data>
</response>

/v1/shorten?username=USERNAME&password=PASSWORD&uri=http://example.com/&format=txt

http://short/lqC

There is no limit on the number of calls from a single IP or user. It's not a complete and secure implementation to run as a public service. But in my case I needed this for use within another application (which has it's own user with only the "use shorturl" permission), which is just fine.

I will suggest to commit this to CVS (after reviewing of couse) this way, or maybe in a separate module, but with adding a note somewhere that this feature is not intended for public usage.

Adding a keyword to the title to make this issue easier to find.

sub

Rerolled patch for version 1.2

@mauritsl,

looks great. Many thanks. I am going to try to commit this as soon as I can test. If somebody else can help with testing, that would be awesome, of course.

This issue was filed against the previous Drupal 6/7 module that used this project namespace.

The namespace has been taken over and the module has been replaced by a completely new and unrelated project for Drupal 10/11.

The original code remains available in the 6.x-1.x branch.

Closing this issue as it no longer applies to the current module.