W liście Damian z dnia czwartek, 16 kwietnia 2009: > What does specifying protocol=https do exactly? Replace http:// with > https:// to the url? > > That tells the browser to go look for a given url at port 433. I'm > guessing for most purposes it would be sufficient to ask routes to > generate a custom port number when 'https' is specified. > Not really. https:// tells the browser to use https, not http, that is, to turn on encryption. In addition it changes the default port from 80 to 443
So, if eg. port 8080 uses https then http://somesite:8080/ won't work, while https://somesite:8080/ will. One could even run http (not https) on port 443, byt this is a bad idea. -- Paweł Stradomski --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
