Something like:
find /www/vhosts/www.example.com -type f -exec sed -i
's/old\.example\.com/new\.exampl\.cond/g' {} \;
No?
On Wed, Oct 31, 2012 at 4:31 PM, David3 <[email protected]> wrote:
> I don't know if it's the best solution,
> I would copy the whole folder and do a deep replace in files with localhost
> to be quick.
>
> Sent from my mobile
>
> On 31/ott/2012, at 17:15, Patrick Laverty <[email protected]> wrote:
>
>> Ok, newbie here...
>>
>> I was asked to scan a web site that we were told is vulnerable. So I'm
>> copying the site over to my Dev server and each time I manually click
>> on links, I see it sends my request to production. I went through the
>> .htaccess file and changed everything to point to my Dev server. It
>> still goes to prod. I dig in a little further and sure enough, most of
>> the links in the hundreds of pages are hardcoded to the prod site.
>>
>> What's the safest way to get around this? Set the /etc/hosts file on
>> my scanning machine to point to my Dev server? I want to make 100%
>> sure that my scan never hits the production server.
>>
>> Suggestions?
>>
>> Thank you.
>> _______________________________________________
>> Pauldotcom mailing list
>> [email protected]
>> http://mail.pauldotcom.com/cgi-bin/mailman/listinfo/pauldotcom
>> Main Web Site: http://pauldotcom.com
> _______________________________________________
> Pauldotcom mailing list
> [email protected]
> http://mail.pauldotcom.com/cgi-bin/mailman/listinfo/pauldotcom
> Main Web Site: http://pauldotcom.com
_______________________________________________
Pauldotcom mailing list
[email protected]
http://mail.pauldotcom.com/cgi-bin/mailman/listinfo/pauldotcom
Main Web Site: http://pauldotcom.com
