Jump to content

Search the Community

Showing results for tags 'web server'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Welcome
    • Announcements & News
    • New Arrivals
  • Web Development
    • Programming
    • Database Development
    • Server Administration
    • Hosting & Domains
    • Frameworks
  • Web Design
    • HTML & CSS
    • Graphics & Multimedia
  • Desktop Discussion
    • Linux Development
    • Windows Development
    • Mac/Apple Development
    • Hardware Discussion
  • Marketing & Business
    • Advertising, Marketing, Monetization & Social Media
    • Search Engine Optimization & Traffic Building
    • Buy, Sell or Trade
  • Prodjex Web Development Applications, Tools and Plugins
    • IP.Board Applications and Plugins
    • Web Tools
  • The Developer Dump
    • General Chat

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 3 results

  1. As a website consultant I have seen that many of my clients would wait for the last day when the opt in for renewing their Web Hosting Subscription. Despite the fact that many of these Web Hosting Providers have a Auto Renew kind of feature enabled, yet, it remains something which many of my clients do not prefer. They cite different reasons - Privacy, unease of sharing credit card information and even what if they close out or go rogue! - yeah, weird ones too come across! I, however, on the other hand, always recommend that you keep your hosting update with the payments to avoid the last
  2. I know this is a pretty basic thing, but I've seen so many tutorials out there that are non-dynamic solutions. Normally when you google "How to force HTTPS using an .htaccess file" or "Redirect HTTP to HTTPS using an .htaccess file" you get examples like the below. RewriteEngine On RewriteCond %{SERVER_PORT} 80 RewriteRule ^(.*)$ https://www.example.com/$1 [R,L] This does work, but you have to replace www.example.com with your domain and it's then hard-coded and not dynamic. I don't like hard-coding anything unless it's absolutely necessary, so here's an example of the dynamic w
  3. Check out the DeveloperBase guide to setting up your cPanel getting ready for your website: http://youtu.be/rWcos_uJ5lE
×
×
  • Create New...