[bd] Attachment Store [Deleted]

I was just navigating there. It doesn't work by .htaccess, it works by the control panel of the CDN itself.
Navigating to
cdn.mydomain.com/attachments/12760/
Shows me the image if I log in.
I just need to confirm if the add on produces that CDN URL. But you said that you navigate there by yourself so it's all good.

Back to your question, no, CDN will not cache that attachments/12760 URL.

You will notice that you get redirected to another URL if you login and go to that URL. CDN will cache the second URL (the longer one with a file name).
 
I just need to confirm if the add on produces that CDN URL. But you said that you navigate there by yourself so it's all good.

Back to your question, no, CDN will not cache that attachments/12760 URL.

You will notice that you get redirected to another URL if you login and go to that URL. CDN will cache the second URL (the longer one with a file name).
So I'm just curious. Since cdn.mydoamin.com/data/attachemnt/whatever
doesn't follow permissions if it's accessible directly - is there a way to guess/get the cdn link from outside(without having the right permissions)?
 
So I'm just curious. Since cdn.mydoamin.com/data/attachemnt/whatever
doesn't follow permissions if it's accessible directly - is there a way to guess/get the cdn link from outside(without having the right permissions)?
No way to guess. But a user with proper permission can leak that URL for others.
 
I'm wondering if it's just me or a bug. Since moving all my attachments to the data folder, the counter that is present below a thumbnail in a specific post isn't working (it doesn't count viewers anymore. It stays on zero).
I'm referring to this:
http://img545.imageshack.us/img545/8405/atek.png

Can you reproduce this?

Thanks.
This is the expected behavior. User gets the direct link to the file so no view tracking is done.
 
You can enable enforce permission and let all download request go through XenForo first (before being redirected to the actual file). You will need latest version (v0.11, has just released a few minutes ago) to have proper view logging.
Great, I'll check this out.
 
I've noticed a slight problem since the last update.

It looks like images uploaded before the latest update (with the file format option).

It looks like it's re-writing all image URLs to have lower case file extensions. Before this, I had quite a lot of uppercase file extensions.

example:

http://z22se.co.uk/garage/astra-white-pearl-irmscher-selection.44/

upload_2013-10-21_15-56-46.webp

That file is there, but with a UPPERCASE extension:

Code:
[root@nginx 09]# ls -hl 48522*
-rw-r--r-- 1 nginx nginx 2.1M Sep 11 20:32 48522_DSC02259.JPG

This is the URL of the actual file:

http://z22se.co.uk/data/attachment-files/2013/09/48531_IMG_1977.JPG

I've downloaded that, and re-uploaded in a post:

http://z22se.co.uk/data/attachment-files/2013/10/49280_48531_IMG_1977.jpg

It's made the file extension lowercase.

I've installed a test copy running 0.10.1 and uploading the same file keeps the extension CAPITAL

http://test.z22se.org.uk/data/attachment-files/2013/10/4_48531_IMG_1977.JPG
 
I've noticed a slight problem since the last update.

It looks like images uploaded before the latest update (with the file format option).

It looks like it's re-writing all image URLs to have lower case file extensions. Before this, I had quite a lot of uppercase file extensions.

example:

http://z22se.co.uk/garage/astra-white-pearl-irmscher-selection.44/

View attachment 59508

That file is there, but with a UPPERCASE extension:

Code:
[root@nginx 09]# ls -hl 48522*
-rw-r--r-- 1 nginx nginx 2.1M Sep 11 20:32 48522_DSC02259.JPG

This is the URL of the actual file:

http://z22se.co.uk/data/attachment-files/2013/09/48531_IMG_1977.JPG

I've downloaded that, and re-uploaded in a post:

http://z22se.co.uk/data/attachment-files/2013/10/49280_48531_IMG_1977.jpg

It's made the file extension lowercase.

I've installed a test copy running 0.10.1 and uploading the same file keeps the extension CAPITAL

http://test.z22se.org.uk/data/attachment-files/2013/10/4_48531_IMG_1977.JPG
I can confirm the behavior: all extensions are converted to lowercase starting from v0.10.2. However, it should not cause any issues. Are you saying the images doesn't show up for old uploads?
 
I can confirm the behavior: all extensions are converted to lowercase starting from v0.10.2. However, it should not cause any issues. Are you saying the images doesn't show up for old uploads?
Correct. I get a 404 error for all the files with uppercase extensions.
 
Is that happening with old attachments or new attachments or all of them? New vs. old here is relative to version 0.10.2 FYI.
Old attachments uploaded before 11.0 was installed.

Anything with an uppercase extension now doesn't show

image.webp
 
So you meant both old attachments AND new attachments are not working? :eek:
No, new attachments are working, because when the file is uploaded, the extension is also being converted to lowercase. Old attachments with lowercase extensions are also working.
It's old attachments with uppercase extensions that are now not working.

EDIT:

I've just tested this on another site as well, as I thought it could be nginx causing it, but the other site is running on Apache 2.2 so it's not my set up.
 
No, new attachments are working, because when the file is uploaded, the extension is also being converted to lowercase. Old attachments with lowercase extensions are also working.
It's old attachments with uppercase extensions that are now not working.

EDIT:

I've just tested this on another site as well, as I thought it could be nginx causing it, but the other site is running on Apache 2.2 so it's not my set up.
Do you happen to run a rebuild recently? Also, you said you tested on an Apache server, it is having issues too?
 
Top Bottom