I accidentally hijacked my localhost
        Posted  
        
            by 
                Zach L
            
        on Super User
        
        See other posts from Super User
        
            or by Zach L
        
        
        
        Published on 2012-12-13T18:26:14Z
        Indexed on 
            2012/12/13
            23:07 UTC
        
        
        Read the original article
        Hit count: 466
        
Opening localhost in the browser is pointing a local webpage (examplePage) after playing with some config files a while back, and I can't figure out how to restore the default behavior.
Background:
I have XAMPP installed on my Windows 7 machine, and a webpage at c:/xampp/htdocs/examplePage.
A couple weeks ago, I was on a mission to get sites root-relative urls (/resource) to work, so I played around with a bunch of apache/conf files, including httpd.conf and httpd-vhosts.conf and also was messing with the Windows hosts file.  I gave up at some point, didn't document exactly what I did, and have since probably forgotten some of what I did.
Many of my changes stemmed from suggestions in this StackOverflow post
What I've Tried
- I commented out my additions to the 
hostsfile - I turned off XAMPP (thus hopefully negating any apache config file effect)
 - I reverted to my original 
DocumentRootinhttpd.confanyway (xampp/htdocs) 
localhost still displays examplePage.  Even with xampp turned on (my reverted DocmentRootisn't taking effect)
Does anyone know what I may have done and how I can fix it?
Update : Its been resolved, thank everyone so much
- in taskmanager, theres a couple instances of httpd.exe (Apache HTTP Server). I ended these, and opened XAMPP, restarting apache.
 - all references to 
examplePagein my .conf files that I could find had been commented out or removed. I imagine that the old versions were still in effect for some reason, and manually ending the Apache processes fixed this. 
As a point of interest, Its still a mystery why those processes were running - I cannot reproduce that situation. I must've stumbled upon a XAMPP bug of some sort.
© Super User or respective owner