#2207 closed defect (invalid)
Turn off I2P webserver (eepsite) inside Clients
Reported by: | anonymous maybe | Owned by: | str4d |
---|---|---|---|
Priority: | minor | Milestone: | undecided |
Component: | apps/jetty | Version: | 0.9.34 |
Keywords: | Cc: | ||
Parent Tickets: | Sensitive: | no |
Description
i was wondering what is the use of enabling Jetty (net.i2p.jetty.JettyStart? "/home/user/.i2p/eepsite/jetty.xml") by default inside http://127.0.0.1:7657/configclients. while i2p tunnels for jetty is turned off by default inside http://127.0.0.1:7657/i2ptunnelmgr ?
its good that it is turned off by default, but shouldnt that for both? or is there a different ?
- I2P Version and Running Environment
I2P version: 0.9.34-0-2ubuntu1 Java version: Oracle Corporation 1.8.0_162 (OpenJDK Runtime Environment 1.8.0_162-8u162-b12-1~deb9u1-b12) Wrapper version: 3.5.30 Server version: 9.2.21.v20170120 Servlet version: Jasper JSP 2.3 Engine JSTL version: standard-taglib 1.2.5 Platform: Linux amd64 4.14.18-1.pvops.qubes.x86_64 Jcpuid version: 3 Processor: Haswell Core i3/i5/i7 model 60 (coreihwl) Jbigi: Locally optimized native BigInteger library loaded from file Jbigi version: 4 GMP version: 6.1.2 Encoding: UTF-8 Charset: UTF-8
Subtickets
Change History (2)
comment:1 Changed 3 years ago by
Component: | apps/console → apps/jetty |
---|---|
Resolution: | → invalid |
Status: | new → closed |
comment:2 Changed 3 years ago by
As discussed on #i2p-dev
:
<&zzz> On this ticket, what Mtc and others said above is correct. We run the eepsite for the help page and because it uses very little resources. <&zzz> enabling the tunnel when there's nothing but the help page on there would be pointless and use a lot of resources.
Note: See
TracTickets for help on using
tickets.
Please don't use Trac to ask questions. Trac is for bugs. If you wish to debate design choices, please use IRC or a forum.