To provide a networking perspective of thing, 8080 would be an expected and sensible default port for HTTP traffic. If the server is running HTTPS (i.e. notebook(secure=True)) then 8443 would be expected. The main issue I could see with changing the default is that individuals running with the default port may have configured their firewall for port 8000, and will then find their access unexpectly broken upon upgrade if the default port changes.
Adam On Nov 25, 7:50 am, David Kirkby <david.kir...@onetel.net> wrote: > On 21 November 2010 16:05, tuxiano <tuxi...@gmail.com> wrote: > > > I'm not an expert of the matter, but I'm the user who made the comment > > and I'd like to add that I don't have problems with sites that use > >port8080 while I can't connect to sites that useport8000, for > > example I can't connect to > > >http://t2nb.math.washington.edu:8000/ > > I've now set up a filter rule using ipfilter, so you can now access > this onport8080 too. > > So both > > http://t2nb.math.washington.edu:8000 > > and > > http://t2nb.math.washington.edu:8080 > > are the same server. Mainly for my own information, but here is what > was entered to do the appropriateportredirection on a Solaris 10 > SPARC system in the *global* zone. This uses the ipfilter firewall - > other firewalls will use a different syntax. > > r...@t2 # cat /etc/ipf/ipnat.conf > # Allow the server which runs by default on the reservedport8000 > # to be used on the more sensibleport8080. > # 8000 is reserved for remote desktop management (RDM), whereas > # 8080 is reserved as an alternative HTTP sever > # Seehttp://www.iana.org/assignments/port-numbers > > rdr nxge0 128.208.128.196port8080 -> 128.208.128.196port8000 > > # If one wants it onport80 too, that ie easily done too. > #rdr nxge0 128.208.128.196port80 -> 128.208.128.196port8000 > > > So I think that switching from 8000 to 8080 could solve the problem. > > I think that would be the sensible long-term solution. Of course it > will involve some level of backwards incompatibility, but IMHOport > 8000 should never have been used in the first place. > > > I > > repeat that I'm not expert of the argument, I just tell you what > > happens from my office PC. > > I doubt you are the only one unable to get out onport8000 either, > since 8000 is reserved for remote desktop management. > > > > > Thanks and regards > > > Tiziano > > I hope that server is able to fulfill your needs. It's not the fastest > machine in the world, as the CPUs are not really appropriate for > scientific work. But it is quite reliable machine - it has been up > nearly a year without a reboot. > > r...@t2 # uptime > 5:47am up 307 day(s), 14:40, 2 users, load average: 0.14, 0.19, 0.20 > > Dave -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
