your not understanding reverse proxying. the ':3000' is not visible to the outside.
IIS would need to forward the request to the port and then push the response back to you something like this http://www.saltypickle.com/Home/16 is what I am talking about On 24/05/2006, at 8:38 AM, [EMAIL PROTECTED] wrote: > > I don't think the last option (swap the IIS for Apache) like to the > hosting company. Remember: is a shared hosting server, already RUNNING > websites and that thing (the test part is my job, but if that pass ok > this must be a simply thing for theirs)... > > The first option... that not mean that a URL become: > > www.mysite:3000/index? > > Is fine for development or in-house websites but I'm planing run > comercial websites... > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
