fetching an asset called "images.jpeg" fails with 404

[cb]

my drop 'wa8hrsl' contains an image called 'images.jpeg', for which I
would like to fetch the embed code as follows:
http://api.drop.io/drops/wa8hrsl/assets/images-jpeg/embed_code.json?version=1.0&api_key=...

unfortunately, this results in a HTTP 404 error.

what's interesting is that this seems to depend on the file-name. if
the file is called e.g. 'foo.jpeg' instaed of images.jpeg all works
just fine.

what is going wrong here?

regards
Christoph

[Jacob Robbins]

Christoph,
We don't have an answer for you quite yet but we're looking into it
and will get back to you. I've been able to reproduce the 404 on
"images-jpeg" but calling other assets is giving me a 403 so I think
I've got a key issue to sort out first.
-Jacob

> --
> You received this message because you are subscribed to the Google Groups "Drop.io API" group.
> To post to this group, send email to dropi...@googlegroups.com.
> To unsubscribe from this group, send email to dropio-api+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/dropio-api?hl=en.
>
>

[Jacob Robbins]

Christoph,
We've come up with a theory for why this is happening and are
testing out a possible fix in our staging environment. We'll let you
know what happens next.
-Jacob

[Jay Goodman Tamboli]

The problem I'm seeing is that the emails sent via the API all link to
the drops on http://api.drop.io/ instead of on http://drop.io/. For
some reason, http://api.drop.io/whatever, where you can replace
"whatever" with seemingly any string, always gives you the same drop.
E.g. http://api.drop.io/whatever is the same drop as http://api.drop.io/foobar.
Judging from the email address in the sidebar, is it possible someone
created a drop named "API," and that's what we're seeing?

/jgt
-- 
http://tamboli.cx/

[Jay Goodman Tamboli]

Sorry to be a pain about this, but has there been any progress on this
bug? I'm still seeing emails sent via the API linking to, for example,
http://api.drop.io/mvjjqbd/asset/acid-picdump-67-jpg. That URL returns
a 404, but it works if I delete the "api" from the URL. As I said
above, I think http://api.drop.io/whatever is referring to the Drop
named "api." I suggest either http://api.drop.io/dropname should show
(redirect?) the content of http://drop.io/whatever, or the emails sent
via the API should link to http://drop.io instead of http://api.drop.io.

Thanks.

/jgt
-- 
http://tamboli.cx/, PGP key ID 64301A5F

[Jacob Robbins]

so we succeeded in confirming that the source of the original problem
is that the website for developer account management is running on
http://api.drop.io, the same domain that hosts our REST api itself.
The developer account management system is a ruby on rails app which
uses the convention of that framework to put static files in /images
and /stylesheets. As a result, the proxy that domain is incorrectly
handling API requests that include "/images" or "/stylesheets"
anywhere in the URI.

We attempted to restrict the matching to only occurences at the
beginning of the request path however that effort was unsuccessful. So
for the time being "images" and "stylesheets" in api resource names
are still a known problem. We are currently working on moving the
developer UI off of the api.drop.io domain to fix the problem once and
for all. This move will likely happen along with a few other
improvements which are being made to the developer account system in
general.

[Michiel Crefcoeur]

maybe this problem can be solved at the URL rewriting level?

2010/3/31 Jacob Robbins <ja...@dropio.com>

[Jake Good]

We're trying to fix it at the redirect level... We'll get it! Thanks for being patient!

In reference to the previous email with the links, you're forgetting to place another path separators in there...

Example:

This:

http://api.drop.io/mvjjqbd/asset/acid-picdump-67-jpg

Should be:

http://api.drop.io/drops/mvjjqbd/assets/acid-picdump-67-jpg

I know that's not all of the issue here, but please, for reference material, we should all be on the same page so when new people come in, they start off on the right foot!

Jake Good

http://dev.drop.io

[Jay Goodman Tamboli]

On Mar 31, 2010, at 10:14, Jake Good wrote:

> In reference to the previous email with the links, you're forgetting to place another path separators in there...
>
> Example:
>
> This:
>
>> http://api.drop.io/mvjjqbd/asset/acid-picdump-67-jpg
>
> Should be:
>
>> http://api.drop.io/drops/mvjjqbd/assets/acid-picdump-67-jpg
>
> I know that's not all of the issue here, but please, for reference material, we should all be on the same page so when new people come in, they start off on the right foot!

I get an error about an invalid API key when I request the second URL in my browser.

To be clear: the first URL is what I get in an email when I send a link via the send_to action in the REST API.

Here's an example email:

> Greetings,
>
> A drop.io user has sent you a picture.
>
> You can view it on the web at http://api.drop.io/mvjjqbd/asset/acid-picdump-67-jpg
>
> We never send emails that have not been explicitly requested by our users. If you have any questions or concerns, please e-mail us at sup...@dropio.com, or check out our FAQ page at http://drop.io/faq
>
> Regards,
> Team drop.io
>
> http://drop.io | http://drop.io/blog | http://twitter.com/dropio

Perhaps we're talking about different bugs here. My complaint is that the URL in the emails doesn't actually show the asset.

Thanks, and sorry for the confusion.

[Jacob Robbins]

yeah, I was following up on the error in the subject line "fetching an
asset called "images.jpeg" fails with 404", i don't think it relates
to the issue you are seeing with system generated emails.

[Jake Good]

Yeah, that's a small mistake on our side, I'll log the bug, I know
exactly where that goes :)

Jake Good
http://dev.drop.io