MultiformeIngegno

  • Posts: 1,337
Re: Issues with CDN's
« Reply #15, on January 28th, 2014, 12:46 PM »
:o I really didn't remember the proxy setting. I'll try it soon

Nao

  • Dadman with a boy
  • Posts: 16,079
Re: Issues with CDN's
« Reply #16, on January 28th, 2014, 01:00 PM »
:cool:
Posted: January 28th, 2014, 12:56 PM

Pandos, I've sent you a PM about this!

MultiformeIngegno

  • Posts: 1,337
Re: Issues with CDN's
« Reply #17, on January 28th, 2014, 01:18 PM »
Now with CF on sessions work fine even without proxy setting on. I don't know what to say.. <_<

Nao

  • Dadman with a boy
  • Posts: 16,079
Re: Issues with CDN's
« Reply #18, on January 28th, 2014, 01:21 PM »
Lol.

Well, I think that's just a random thing anyway. (i.e., hard to reproduce.)

Did you test the rest of the bugs mentioned by Pandos in his first post?
I'm currently working with him in private to see if my alternative handling of the query string can fix the search problem.

MultiformeIngegno

  • Posts: 1,337
Re: Issues with CDN's
« Reply #19, on January 28th, 2014, 06:29 PM »
Will test the other issues tonight! Any news on the mysql deprecated function of the importer?
Downside of being on latest php ... :P

Nao

  • Dadman with a boy
  • Posts: 16,079
Re: Issues with CDN's
« Reply #20, on January 28th, 2014, 06:59 PM »
Well, I got started on it earlier today, and then got pissed at how annoying it is to convert... You know, some conversions are no-brainers (just add an 'i'), others require switching params... Meh!!
I'll probably finish that tomorrow.
Re: Issues with CDN's
« Reply #21, on January 28th, 2014, 07:01 PM »
Quote from Pandos on January 28th, 2014, 01:19 AM
  • Attachments not showing up
    It looks like those resources are being served out of the reference domain
     with a "Content-Encoding: none" header. This causes some problems with  decoding the response (confirmed by Google).
    But this can be easily fixed.
How..?

Pandos

  • Living on the edge of Wedge
  • Posts: 635
Re: Issues with CDN's
« Reply #22, on January 28th, 2014, 07:15 PM »
Quote from Nao on January 28th, 2014, 07:01 PM
Quote from Pandos on January 28th, 2014, 01:19 AM
  • Attachments not showing up
    It looks like those resources are being served out of the reference domain
     with a "Content-Encoding: none" header. This causes some problems with  decoding the response (confirmed by Google).
    But this can be easily fixed.
How..?
As far as I can see this affects  AeMe too. Just remove Content-Encoding: none and everything is OK :)
Or more elegant: Content-Encoding: image/jpg, png, etc...

In SMF it was in QueryString.php.
# dpkg-reconfigure brain
error: brain is not installed or configured

Nao

  • Dadman with a boy
  • Posts: 16,079
Re: Issues with CDN's
« Reply #23, on January 29th, 2014, 01:03 PM »
But it's there for a reason, innit..?

Pandos

  • Living on the edge of Wedge
  • Posts: 635
Re: Issues with CDN's
« Reply #24, on January 29th, 2014, 01:15 PM »
IMHO it's for compatibility reasons?
You can upload different types of files. To ensure it's not an e.g. executable file, it's obfuscated.
But there's really no need for it?
What should speak against leaving the attached filenames as they are?
They all get obfuscated with a file hash.


This situation makes it really impossible to easily get content to social media networks.
Also serving with the correct content-type is the best and secure thing.
Re: Issues with CDN's
« Reply #25, on January 29th, 2014, 01:22 PM »
By the way. Attachments are already stored with the correct mime type in db. Correct me when I'm wrong, but I see no culprit in it.

Nao

  • Dadman with a boy
  • Posts: 16,079
Re: Issues with CDN's
« Reply #26, on January 30th, 2014, 12:46 PM »
I'm a little slow here. I don't get what you're trying to make me remove, and why you're assuming that it's not needed. :^^;: