Cloudfront and Advanced Mod-Rewrite

Using WordPress 3.3.1
S2 Member Pro v111220

I think I’m writing my Advanced Mod-Rewrite code incorrectly.

I have a pdf file in my Cloudfront bucket that I want to serve inline. I’ve configured the metatags accordingly. If I use the standard code with a query string, it works correctly. But if I use Advanced Mod-Rewrite, I get a server error.

The filename is “howtopresentourlessons.pdf” and for the purpose of this test, I’ve put it on the root level of my bucket, not in a folder. There are no protections on the page containing the link.

And here are the two code samples:

This link uses a query string, and it works (opens the pdf file inline):
<a href="http://rockitscience.com/wordpress/?s2member_file_download=howtopresentourlessons.pdf">How to Present a Rock-it Science Lesson</a>

This link uses Advanced Mod-Rewrite Linkage and doesn't work (server error):
<a href="http://rockitscience.com/wordpress//wp-content/plugins/s2member-files/howtopresentourlessons.pdf">How to Present a Rock-it Science Lesson</a>

Hey,
maybe this causes the problem?

…wordpress//wp-content….

Greetings

Thanks for catching that, Bendix. However, even after I removed the extra slash, I still get a server error.

Hi there. Thanks for your inquiry.
Try it like this please, with the inline specification. Does this help?

http://rockitscience.com/wordpress/wp-content/plugins/s2member-files/s2member-file-inline/howtopresentourlessons.pdf

* Please test in the latest release of s2Member v120213, which resolved some issues with GZIP conflicts, related to protected file downloads.

Changelog here: http://www.s2member.com/changelog/

If problems persist, please let me know what web server you’re running. Is it Apache?

Thanks, Jason. I just tested this in v120213. As I mentioned in another post, the update had crashed my site (yes, it’s Apache/1.3.42). But I found your reply to another post where you suggested alternate code for the .htaccess file, and I pasted that in and got the site back up.

The new code for my file download looked like it was going to work. I got the “confirm file download” dialogue box, but when I clicked Okay, I got a “500 Internal Server Error.”

So sorry for abandoning you here.
It was not intentional. Some of my threads got buried during the new site launch by mistake.

Yes, that’s correct. Also, s2Member v120219 was released shorter thereafter to improve compatibility with the Apache 1.x series. If these issues remain after upgrading to s2Member v120219, I would still recommend that you move into Apache 2.0 or higher.

Okay, I got a “500 Internal Server Error.”

Check your PHP error log. Anything there to tell the tale?