Although I wouldn't mind it, I can foresee this being a problem for some. You're now essentially forcing everyone to use ssl. The ssl right now i believe is going to prompt everyone that it's not a known signed certificate which could be annoying or misleading for a lot of people.
Once again, I wouldn't mind it; but I could see some people having a problem with it. -- Stephen Ostrow On May 5, 11:14 am, Sebastian <[EMAIL PROTECTED]> wrote: > Hello, > > we have a client which has problems doing SVN updates due to their > proxy/firewall. We "linked" symfony to our app using svn:externals, > and we changed from http:// to https://... as svn:externals url due to > these issues. > > The problem is: symfony itself uses svn:externals internally (self- > referencing to other SVN repositories on symfony-project.com): > > doc ->http://svn.symfony-project.com/doc/tags/RELEASE_1_0_14 > lib/vendor/pake > ->http://svn.symfony-project.com/tools/pake/tags/RELEASE_1_1_5/lib/pake > lib/vendor/lime > ->http://svn.symfony-project.com/tools/lime/tags/RELEASE_1_0_4/lib > > Do you think you could change these from http:// to https://? > > I'm not aware of any possible problems, so it would be nice, but it's > your decision :-) > > Thanks for your time, > > Best regards, > > Sebastian > > On Mar 7, 10:04 pm, isleshocky77 <[EMAIL PROTECTED]> wrote: > > > Thank you very much. Now I'll be able to update some of the plugins I > > work on. > > > On Mar 7, 1:14 pm, Fabien POTENCIER <[EMAIL PROTECTED] > > > project.com> wrote: > > >https://svn.symfony-project.com/isnowonline. > > > > Enjoy! > > > Fabien > > > > -- > > > Fabien Potencier > > > Sensio CEO - symfony lead developer > > > sensiolabs.com | symfony-project.com | aide-de-camp.org > > > Tél: +33 1 40 99 80 80 > > > > isleshocky77 wrote: > > > > Fabien, > > > > Is there any update on this topic? > > > > > On Feb 23, 6:29 am, Fabien POTENCIER <[EMAIL PROTECTED] > > > > project.com> wrote: > > > >> Hi, > > > > >> Thanks for the info. We will setup SSL on the symfony SVN in the coming > > > >> days. So, expect to be able to usehttps://svn.symfony-project.com/soon. > > > > >> Fabien > > > > >> -- > > > >> Fabien Potencier > > > >> Sensio CEO - symfony lead developer > > > >> sensiolabs.com | symfony-project.com | aide-de-camp.org > > > >> Tél: +33 1 40 99 80 80 > > > > >> isleshocky77 wrote: > > > >>> Here is the the faq from subversion. > > > >>>http://subversion.tigris.org/faq.html#proxy > > > >>> ". > > > >>> Another strategy is to attempt the checkout over SSL, which many > > > >>> proxies allow: > > > >>> svn checkouthttps://svn.collab.net/repos/svn/trunksubversion > > > >>> " > > > >>> And like I said, it shouldn't be hard or time consuming to set up a > > > >>> copy of the svn server on ssl. It doesn't matter if it's a dummy > > > >>> certificate. > > > >>> On Feb 22, 7:11 pm, "Ian P. Christian" <[EMAIL PROTECTED]> wrote: > > > >>>> isleshocky77 wrote: > > > >>>>> I guess no one ever runs into this problem while trying to commit to > > > >>>>> the repository? > > > >>>> no, I've not heard of any issues related to non-ssl HTTP user > > > >>>> (remember, > > > >>>> SVN over HTTP is simply HTTP with different verbs, nothing special) > > > >>>> I think it's just you and your odd firewall ;) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
