|
[
Permalink
| « Hide
]
Eloy Lafuente (stronk7) added a comment - 05/May/08 05:48 AM
Good idea. Assigning this to Petr... thanks!
sorry, I do not understand this part "from the proxy where a proxy has been set up".
Are you talking about Moodle server behind a proxy? Or people accessing internet server from behind a proxy? Also I do not understand why any restrictions of this kind would be "really useful"? Do you mean secure? I always thought that firewalls with DMZs are easier to set up and more secure. I guess Howard is talking about Moodle (the program) accessing to information stored in other computers (could be other mnet hosts, or webservices or filelib... ) any piece of code currently supporting $CFG->proxyhost.
The key is that not all those outgoing connections must be performed using the proxy (other intranet hosts, for example, need to be accessed without the proxy), and that's what Howard is proposing, if I'm not wrong. Ciao Yes, Eloy is spot on - sorry if I wasn't clear.
Without being able to make exceptions every HTTP call that Moodle makes out will have to go through the proxy. PS. Happy to produce some code for this for review. Of course, it means hooks all over the place. Yes - that was my worry too with MDL-14624. I think I agree - I'll back that out of stable, and fix the whole thing properly in HEAD.
Changes added to HEAD. AFAIK, this only seems to effect lib/filelib.php and mnet/lib.php. I couldn't see anything else that did outgoing HTTP requests. If anybody knows different, please let me know and I'll add them.
This functionality is now in HEAD. Please reopen if I missed anything.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||