Jump to content

Search the Community

Showing results for tags 'apache'.

  • 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. Recently a client buy a VPS at 1&1 and I moved the Worpress site from old shared hosting (Bluehost) to new VPS. The site is extremely slow and I don't know how to fix this meaning where to attack, if I should optimize something in Apache, if I should install some plugin to avoid this or something else so I need some advice. Some data around that WP: Database hold around 35k posts I have disable W3C Total Cache plugin since I think is miss configured and can slow down the site I have not using any image compressor like thimbthumb (this was installed in first but due to s
  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. In Laravel the path for serving your web page is in the /public folder. By default after installing Laravel and navigating in a browser to the URL you will see a directory listing of all the Laravel files. Here’s an easy way using an .htaccess file to redirect requests to the Laravel /public folder user mod_rewrite. Create a .htaccess file in your root directory and add the following code. RewriteEngine on RewriteCond %{REQUEST_URI} !^public RewriteRule ^(.*)$ public/$1 [L] Save your file and refresh your browser, you should now see the default Laravel splash page.
×
×
  • Create New...