|
Posted by murrayatuptowngallery on 01/19/07 17:05
Wow, this is an active group...I had to dig to find my post!
How I saw php source (or think I saw it). Simplest 'Hell oWorld'
dumb-beginner script, uploaded as test.php and FTP'ed it to the ...I
hesitate to call the directory Root, because that's probably not
correct...the it was the directory/folder where all the
public-accessible stuff is. I believe my host co. has some areas called
public something, an area called www and an area called html.
Two of them 'mirror?' each other...that is, if I put a file in one I
find it in the other too...off the focus here, but struck me as
strange.
So, after I saw the 'Hello World' message appear, I did View Source and
>thought< I saw code....I won't put money on it being the php part, but I now of course realizee there HAS to be some sort of markup language output for the browser to react to. On such a crudely simple test script, there wasn't alot of php content. Maybe I should look again.
So, regarding the comment, paraphrased 'unless something was configured
incorrectly, I should not see php, just the output'...would placing the
..php file in an accessible but 'wrong for the task' directory
constitute an improper configuration?
I like the obfuscation idea, but since my programming probably already
qualifies as obfuscated, I've been leery of sabotaging my ability to
read it myself the next time I need to modify it. How does one
UN-obfuscate code? Maybe just be organized and keep an unobfuscated
copy, modify it, upload it again, then obfuscate it for safe-keeping?
Thank you.
Murray
[Back to original message]
|