nginx/apache locally served facebook profile #DeleteFacebook
Hi,
We've decided to #DeleteFacebook and downloaded all the household's data in 4 separate zip files.
I've then moved the files to both nginx and apache and get the same problem on both.
The files supplied by FB use relative paths in them. If I click 'photos' or 'messages' down the left hand side, it will display fine, but then if I change sections to 'videos' or whatever, it breaks.
eg. I load up the profile main page hxxp://server/profile1/index.htm and it loads correctly. I click 'Videos' from the side menu on the left and it correctly serves hxxp://server/profile1/html/videos.htm. I then click 'Messages' from the side menu and it attempts to serve hxxp://server/profile1/html/html/messages.htm which fails. It's happening because the side bar is requesting html/message.htm and that is relative to the hxxp://server/profile1/html folder that the previous file was served from.
How do I tell nginx or apache that all requested relative paths should be relative to hxxp://server/profile1 and not whatever sub-directory has been served already? Or can I not do that and I need to re-write the URL instead?
IE & Chrome handle it fine when it's served from a local folder on my laptop. It's that behaviour I would like to emulate if possible.
Sorry if these are noob questions, web servers aren't really my thing.
Thanks,
bored.
|