Problem with plugins

Post by **garvinhicking** » Sun Jan 14, 2007 2:56 pm

Hi Neut!

Finally I had the time to check your server.

My findings are that your provider is blocking the fetch of remote PHP code. As soon as it finds the string "<?php" it denies the request, it seems.

Thus your provider must use a firewall or content-based filter proxy, or tools like mod_Security, that block the call(s).

Sadly this means you have to convince your provider of disabling this, or you cannot use Spartacus.

The upside of your providers method is, that you can't easily be hacked by other people loading PHP-Trojans onto your site.

Best regards,
Garvin

Neut · Post by **Neut** » Sun Jan 14, 2007 3:06 pm

Hi, thanks for your time. I'll check if my webhost can make an exception for my account, if not.... I guess the must be the modern Crassus (who killed Spartacus).

Neut · Post by **Neut** » Tue Jan 16, 2007 12:54 pm

My webhost cannot make the necessary changes, because they fear to compromise the safety for all users (and they are right of course).

Hopefully this problem can be solved in future versions of Spartacus.

Post by **garvinhicking** » Tue Jan 16, 2007 1:48 pm

Hi!

No, this problem cannot be solved at Spartacus! It needs to transfer code, and if your webhost denies this, there is no way to make it work, I'm sorry.

And I agree, they are right about compromising. In a safe environment, Spartacus sadly has no place.

Best regards,
Garvin

judebert · Post by **judebert** » Thu Jan 18, 2007 8:28 pm

Hmmmmm hm hm hmmm hmmmm! (Bubble Bobble danger music.)

If the problem is the <?php tag, couldn't we offer compressed versions of the plugins for SPARTACUS to download, and uncompress them at the blog?

Post by **garvinhicking** » Thu Jan 18, 2007 9:22 pm

Hi!

Uncompressing is often not available and creates memory issues and even more security risks...so I'm afraid that might not be the way to go

Best regards,
Garvin