Tag Info

Hot answers tagged

3

http://www.example.com/ and http://www.example.com are the same URL. Whether or not the trailing slash is shown in the browser address bar is purely cosmetic - when the request is sent to the server the slash will be included. (http://www.example.com/foo and http://www.example.com/foo/ on the other hand are different URLs.) If the site you're working on is ...


2

In your server config, you can modify your current example to include the /abc/ directory to restrict redirects to that one directory: RewriteRule ^/abc/(.*)/(\?.*)?$ /abc/$1$2 [R=301,L] I've removed the backslash escape from the slash, in your example, as this would appear to be unnecessary. Note that to make this work in .htaccess you would need to ...


2

So there are already some answers given. For the second set, the one with the http://url in the request, these tries to find badly configured (not secured) proxy servers that could be wide open. These can then be used to hide the real origin of attacks/scans directed onto an other machine. The other machine will then see the attack as if it was coming from ...


1

Editing MAC's host file You will first need to edit your operating systems host file, on a mac this is a rather simple procedure that you should be able to follow with ease. Open your terminal application (normally /Applications/Utilities/Applications.app or you can may even perfer to use your standard text editor. In the terminal type nano ...


1

To get a website up at a domain name you need to follow these steps: Register the domain name. At the registrar, point the NameServer (NS) records to the domain name server (DNS) that will be handling the domain. On the name server, add records to resolve the host name to your server. Configure your web server to handle requests that come in for that ...


1

Okay. Most of these access (at least) are landscaping attempts to find potential vulnerabilities on your server. They are trying to fingerprint your server to know what web-based applications are installed. The first set and third set are clearly landscaping. The second set may be a result of forged request headers but still likely to be landscaping- not ...


1

It is not exactly the answer to your question but you should think twice about removing trailing slashes for directories. The doc about DirectorySlash warns from potential problems (a mess with relative urls and others). And you can save some headaches by only redirecting with a 301 /dir/index.html to /dir/ (nearly your point 3), and using DirectoryIndex ...


1

Aren't your last two entries cancelling each other out? # Redirect /foo to /foo/index.html then the other way # Redirect /foo/index.html to /foo If it just for those individual files? Then I'd try: # 301 Redirect /foo/index.html to /foo RewriteCond %{QUERY_STRING} ^$ RewriteRule ^foo/index\.html$ /foo? [R=301,NE,NC,L] # 301 Redirect /foo/ to /foo ...


1

It appears that the first issue had to do with skype. The second issue that I was having was some issues in the Apache server.xml. I reverted the xml file to its original state and everything started working without any issues. If port 80 is not working for you just make sure that you change skype so that it no longer uses port 80. Thanks for the help :)


1

I believe the problem here is not likely to be related to your Apache configuration but in your PHP script. For example, if your script loads the entire video file in one go, and then sends it all to the browser in one go this can cause this issue: <?php header( 'Content-Type: video/mp4' ); $sVideo = @file_get_contents( ...


1

The range header handling code is probably where the issue lies, although it's hard to say for sure. Serving videos with PHP tends not to be very memory efficient, particularly if they are large. I'd suggest you use something like X-Sendfile instead. That way, you still do your authentication checks in PHP, but you get your web server to do the heavy lifting ...


1

I see some problems with your rewrite rules. You don't explicitly turn on mod_rewrite with RewriteEngine On When using rewrite rules in your .htaccess file the slash at the beginning of them is assumed. Having a slash at the beginning of the rule will prevent rewrite from executing the rule. (This is different than if the rule were in httpd.conf where ...


1

Apache doesn't recommend using domains in the <VirtualHost> declaration, I have found from experience that you will have far less trouble using an asterisk here (*) and just let the domain be matched against the ServerName value. Also, the first virtual host site behaves as a default for whenever the name does not exactly match one of the defined ...


1

webpagetest.org tests reflect a user loading a page in a web browser - the results can vary from time to time for many reasons that will be out of your control. Following their tips will help you to improve this, though I would strongly recommend carefully thinking about when and how you load javascripts to reduce TTFB. Read more: Feed the Bot: PageSpeed ...



Only top voted, non community-wiki answers of a minimum length are eligible