@Kisuke3
You wrote:
"Add a new rule, name it "WebProcess" and in the port put in there 80 add a new rule again, name it "WebProcess" and in the port put in there 443."
It might be helpful to those less knowledgeable if you specify the navigation route you used to add the new rules. Likely, this is unfamiliar territory for some.
HERE IS SOME ADDITIONAL INFO that might help with this issue of Safari 5.1 and Lion:
In another Apple Discussion [https://discussions.apple.com/thread/3193055?start=15&tstart=0 -- "Safari 5.1 not working on 10.6.8"] here is a comment originally posted by Brett Stewart, and then slightly amended by me. Although it is directed at OS 10.6.8, it might also apply to OS 10.7:
Brett, your solution worked fine for me, too. THANK YOU!
However, for those who might wish to follow your navigation route, I found it to be correct right up to the name of the app.
Maybe it used to be named "WebProcess.app" . . . but in my OS 10.6.8 it is named "PluginProcess.app".
"PluginProcess.app" is the app that's in the "WebKit2.framework" folder.
So, the navigation route is:
Go to System Prefs/Security/Firewall/ Advanced.
Click the plus button to add an allowed process to the firewall.
Navigate to the PluginProcess.app (boot/system/library/Privateframeworks/WebKit2.framework/PluginProcess.app)
Add this to the firewall's allowed processes.
According to the above, the app in question -- on your computer -- might be named "WebProcess.app" or it might be named "PluginProcess.app." In either case, follow the navigation route shown above, and "Allow" it.
I haven't, as yet, upgraded to 10.7; still using 10.6.8. However, like I said, the above information might be relevant for Safari 5.1 on OS 10.7 as well as on 10.6.8.
--David Purnell