Jump to content

Byron

Moderators
  • Posts

    9,153
  • Joined

  • Last visited

  • Days Won

    146

Everything posted by Byron

  1. Not at this time. We don't allow exec().
  2. That should happen within the next 3 months if all goes well and we should be able to offer more features.
  3. I believe you hit the nail on the head djbob. Yeah it makes way more sense to use the "File" tag directive than to use IndexIgnore with sensitive files. Thanks djbob for clearing this up for both of us.
  4. You maybe right about it using order deny, allow, but I really couldn't say for sure. I'll see if I can talk djbob into coming over here when he gets time to answer your question since he's the one who configured the server. In the meantime you might want to check out some more htaccess directives you can use for your htaccess file. http://httpd.apache.org/docs/2.2/
  5. ALWAYS put it at the top of your page right before the doctype (below). <?php if (substr_count($_SERVER['HTTP_ACCEPT_ENCODING'], 'gzip')) ob_start("ob_gzhandler"); else ob_start(); ?> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <title>My test page</title> </head> You'll never see that php code in the source of the page. Just a space before the doctype. And I guess you already know that the page has to have a .php extension.
  6. Yes and its done with Apache mod_autoindex and that would also include dot files like your .htaccess. No problem!
  7. Do you really want to go to war with this young lady? Have you never heard, "Hell Hath No Fury Like A Woman Scorned!" Besides it's not manly to make a women look bad.
  8. The server is set up default not to display error-log files via directory indexing. That error in your log files is normal. You should be able to see ANY file via FTP as long as your logged in. Don't worry about it. You really don't want error log files displayed to the public anyway. You also need to go back and chmod your directory back to 755. You never need to go higher than 755 on any of your directories.
  9. I'm still not seeing any 500 errors even after I click onto some of your links.
  10. I've never used symlink() but just looking at your code, shouldn't you be defining a variable that says: $target2 and $link2 also make sure your paths are correct.
  11. I'm seeing your page just fine. Refresh your cache.
  12. Can you post a php page for us to check?
  13. You know you'll need a dedicated ip to have SSL on your site don't you? Try clearing your cache and see if it's still showing your old domain.
  14. I'm not sure I understand what you mean by CSR's but everything at your cpanel should reflect your new domain name. Check again this morning for me and if it's still not saying your new domain name I'll escalate this.
  15. This support request is being escalated to our root admin.
  16. That was one of the options discusssed in that page you posted. I've tried it on a couple of pages of mine and then tested them and they seemed to check ok. Add that piece of code to one of your pages and take it to this test tool: http://www.gidnetwork.com/tools/gzip-test.php That was posted by djbob and I really didn't look into doing what he said although I'm sure it can be done. I would just add the code I posted to the top of the page instead. This code came from the page you posted. The only difference is they have it in an if statement checking to see if the browser accepts gzip. <?php if (substr_count($_SERVER['HTTP_ACCEPT_ENCODING'], 'gzip')) ob_start("ob_gzhandler"); else ob_start(); ?>
  17. Ashoat said he would rather not bother with adding the module: http://www.helionet.org/index/index.php?showtopic=5583 but you can still use gzip compression by adding this to the top of any php file: CODE<?php ob_start("ob_gzhandler"); ?>
  18. Do you mean php.ini? Which ever configuration file your referring too, you don't have access to any server php configuration files.
  19. You don't need permissions 777 on a folder. 755 will be adequate. There shouldn't be any files inside ypur www folder. All files should go in your public_html folder. Your www will reflect what is in the public_html folder. Great!
  20. This support request is being escalated to our root admin.
  21. Yeah I also noticed the server under a heavy load this morning. I wasn't even able to go to my site for about 10 minutes at around 10:45 am EST.
  22. You might. I'm not sure if simple subdomains are immediate or not. This subdomain another.makelovenotwar.heliohost.org will point to this directory: makelovenotwar.heliohost.org/another It will either open up to your index page or list that directories contents depending whether or not you have an index page.
  23. OK your new domain is now: odgara.co.cc give it 24 hours to resolve and make sure you point your domain to our nameservers.
  24. It does that sometimes when the server load is high. Try it again and if your still having a problem, try again in an hour.
×
×
  • Create New...