Plugin: Jetty Web Server 2.0

[jreichen]

Originally Posted by paulie

Hi jreichen
When I enter http://192.168.2.*:8080/apps, I get the following error.

HTTP ERROR: 404

Problem accessing /apps. Reason:

NOT_FOUND

Powered by Jetty://

Jetty does not seem to be working for me. All looks as it should but always the same error.

Can you try my suggestion back in post #110?

[dmegatool]

Just wanted to let you know that my ISP is blocking the port 80 so that was my problem... Everything is working now. AWESOME plugin !!! Great work !!!

[bcjenkins]

What is the expected behavior of http://server/ ?

When browsing to the root, I get the following:

Error 404 - Not Found.

No context on this server matched or handled this request.
Contexts known to this server are:
/ ---> org.mortbay.jetty.handler.ContextHandler@13d8346{/,file:/opt/sagetv/server/jetty/static}
/sagem ---> org.mortbay.jetty.webapp.WebAppConte...SageWebApp.war}
/stream ---> org.mortbay.jetty.webapp.WebAppConte...aStreaming.war}
/apps ---> org.mortbay.jetty.webapp.WebAppConte...bapps/apps.war}

When I go to apps, etc, it seems to work. The static directory does not exist, fwiw.

B

[robogeek]

Originally Posted by bcjenkins

What is the expected behavior of http://server/ ?

When browsing to the root, I get the following:

When I go to apps, etc, it seems to work. The static directory does not exist, fwiw.

B

I think that's the default behavior. Any external internet traffic (ie. hackers) hitting your machine will get an error and hopefully move on. If you don't like the ugly error, you can do what I did and create a static welcome page. But that's an open invitation for a hacker. If the static directory (SageTV\jetty\static) doesn't exist, create it, and then add your own index.html there. You can create a blank index.html file to get rid of the error but not give anything interesting away to any wouldbe hackers. Or you can create an index.html with an http-redirect that redirects to the apps page. I created a page with logos of most of the SageTV related software and hardware I use and a logon link that links to the apps page. This is what it looks like (larger image is attached):



Zip file with html source code and images is here. Just extract it to the jetty\static directory.

<EDIT>
I have updated my static start page to better match the new Apps and Mobile Web UI dark style. Here is a screenshot of the new static start page style:



Zip file with html source code and images for the new dark style static page is here. Just extract it to the jetty\static directory.
</EDIT>

To all: Please post your screenshots if you create your own static welcome page or modify the ones I have provided

[jreichen]

That's the "expected" behavior. Maybe not the best, but that's Jetty's default. Like most things I can probably customize it. I didn't put a landing page there because I was used to how nielm's TJWS web server didn't put anything at the root.

There should be an empty static directory. I just checked and it looks like it's created on Linux but not Windows. I originally created that so there was a place to put the crossdomain.xml file for shadeblue's web remote. It can be used to server other files as well.

[xj-boonie]

Originally Posted by bcjenkins

What is the expected behavior of http://server/ ?

When browsing to the root, I get the following:

Quote:
Error 404 - Not Found.

No context on this server matched or handled this request.
Contexts known to this server are:
/ ---> org.mortbay.jetty.handler.ContextHandler@13d8346{/,file:/opt/sagetv/server/jetty/static}
/sagem ---> org.mortbay.jetty.webapp.WebAppConte...SageWebApp.war}
/stream ---> org.mortbay.jetty.webapp.WebAppConte...aStreaming.war}
/apps ---> org.mortbay.jetty.webapp.WebAppConte...bapps/apps.war}

When I go to apps, etc, it seems to work.

B

I get a similar respose. I got apps working, but after a couple hours, it's not working - i don't get an error, it just takes forever and then says server took too long to respond. It still works from localhost though. Any ideas?

[bcjenkins]

Originally Posted by jreichen

That's the "expected" behavior. Maybe not the best, but that's Jetty's default. Like most things I can probably customize it. I didn't put a landing page there because I was used to how nielm's TJWS web server didn't put anything at the root.

There should be an empty static directory. I just checked and it looks like it's created on Linux but not Windows. I originally created that so there was a place to put the crossdomain.xml file for shadeblue's web remote. It can be used to server other files as well.

I use linux and the static directory did not create for me automatically. Regarding what it does, I would recommend having a quick redirect page to a logon page or something. I will likely force a redirect to /apps.

Can you enforce SSL too?

Thanks,

B

[wayner]

One thing that could use some work in the web server is the Media Library. It would be nice to be able to browse photos by folder, for example. The same with your video library - it would be great to be able to browse and then click on a file to get it to play in a client.

[jreichen]

Version 2.1.0 is now available. This has a fix that will hopefully eliminate the HTTP 404 and 503 errors related to the webapps directories not being cleaned up.

• SageTV v7-style interface for 'apps' web application (switch from blue to gray as well as other style changes)
• Remove duplicate timestamps on Jetty's log entries in the SageTV log file.
• Override Jetty's war file extraction logic to address HTTP 404 and 503 errors.

Jason

[wayner]

It looks good - now if Sage would just follow your lead and change their startup screen for Sage (and the extenders) so that they follow the Sage 7 "branding" and not look straight out of 2003 that would be good!

Is there a way to Customize the /apps Jetty web home page? I have two servers and, at a minimum, it would be nice to put the server name on the page. (Right now it is obvious because I have updated my main server so it is gray but the backup is not yet upgraded and is still blue). It would also be nice to throw in links to other pages, or even my other server.

[bcjenkins]

A static directory is still not created in Linux - FYI

B

[thomaszoo]

Originally Posted by jreichen

Version 2.1.0 is now available. This has a fix that will hopefully eliminate the HTTP 404 and 503 errors related to the webapps directories not being cleaned up.

I just started getting the errors with the Mobile Web Server the other day. Tried uninstalling and reinstalling it. Then I see this and the easy upgrade fixed the problem

Thanks for the great work.

Wayne

[voorhees]

Originally Posted by jreichen

Version 2.1.0 is now available.

jreichen, I upgraded a couple of days ago to v2.1.0.7 and noticed my SageTV Web Applications page lists my version of SJQ as v4.0.0.1326, however I am actually running v3.1.0.930. When I click on the link from the SageTV Web Application page for SJQ it goes to my SJQ v3 web page just fine, it justs lists the SJQ version number as a newer version which I have not installed. The previous versions of the Jetty Web Server SageTV Web Applications page listed the SJQ version correctly. I guess it is not a big deal since everything still works, but I thought I would point out the issue. Is there anything I can do to update the SJQ version number of the SageTV Web Applications page to the correct one?

Thanks for the great app.

[razrsharpe]

Originally Posted by voorhees

jreichen, I upgraded a couple of days ago to v2.1.0.7 and noticed my SageTV Web Applications page lists my version of SJQ as v4.0.0.1326, however I am actually running v3.1.0.930. When I click on the link from the SageTV Web Application page for SJQ it goes to my SJQ v3 web page just fine, it justs lists the SJQ version number as a newer version which I have not installed. The previous versions of the Jetty Web Server SageTV Web Applications page listed the SJQ version correctly. I guess it is not a big deal since everything still works, but I thought I would point out the issue. Is there anything I can do to update the SJQ version number of the SageTV Web Applications page to the correct one?

Thanks for the great app.

not that this will be much help in fixing the issue... but... my /apps page is listing the same as you for sjg (i have 3 installed). My guess is that jreichen is pulling the info from the plugin manifest, which will have 4.x as the current version... but obviously in our case is not the installed version

[jreichen]

Originally Posted by bcjenkins

I use linux and the static directory did not create for me automatically. Regarding what it does, I would recommend having a quick redirect page to a logon page or something. I will likely force a redirect to /apps.

Can you enforce SSL too?

Thanks,

B

You can add the data constraint line to the context.xml file after the authenticate line. I'm not sure of a way to do it server-wide.

<Set name="authenticate">false</Set>
<Set name="dataConstraint">2</Set>

The non-SSL port will still run but you'll be redirected to the SSL port.

[jreichen]

Originally Posted by wayner

Is there a way to Customize the /apps Jetty web home page? I have two servers and, at a minimum, it would be nice to put the server name on the page. (Right now it is obvious because I have updated my main server so it is gray but the backup is not yet upgraded and is still blue). It would also be nice to throw in links to other pages, or even my other server.

You should be able to copy the files from the jetty/webapps/apps/webapp folder to the jetty/static/apps folder and modify them. The server should find the files in the static directory first and serve them up.

[jreichen]

Originally Posted by razrsharpe

not that this will be much help in fixing the issue... but... my /apps page is listing the same as you for sjg (i have 3 installed). My guess is that jreichen is pulling the info from the plugin manifest, which will have 4.x as the current version... but obviously in our case is not the installed version

Kind of I'm using a Sage API: PluginAPI.GetPluginVersion(plugin). I don't know how it works but it looks like there's a bug. I'll investigate and enter a bug for the Sage devs.

[razrsharpe]

Originally Posted by jreichen

Kind of I'm using a Sage API: PluginAPI.GetPluginVersion(plugin). I don't know how it works but it looks like there's a bug. I'll investigate and enter a bug for the Sage devs.

... looking at the api it looks like there isn't a way to get the installed version and the latest version in the repository (at least with my quick read of the docs anyway...) The STV displays both versions though... so who knows how they are doing that

One other thing i noticed... BMT does not report a version on the /apps page... not a big deal but figured id mention it anyway

[jreichen]

Originally Posted by razrsharpe

... looking at the api it looks like there isn't a way to get the installed version and the latest version in the repository (at least with my quick read of the docs anyway...) The STV displays both versions though... so who knows how they are doing that

Thanks, I'll check the STV code and see if I'm doing something wrong.

Originally Posted by razrsharpe

One other thing i noticed... BMT does not report a version on the /apps page... not a big deal but figured id mention it anyway

I'll mention it to stuckless. The context xml files have to provide the plugin id.

[tmiranda]

Originally Posted by jreichen

Kind of I'm using a Sage API: PluginAPI.GetPluginVersion(plugin). I don't know how it works but it looks like there's a bug. I'll investigate and enter a bug for the Sage devs.

Going from memory, that API returns the latest version that is available in the repository, not the installed version. I think I had to write some custom java code to ge tthe version that was actually installed. It's been a while so don't take my word on that.

Tom