mldonkey-bugs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Mldonkey-bugs] [Bug #3296] [enhancement] why not use relative refs in


From: nobody
Subject: [Mldonkey-bugs] [Bug #3296] [enhancement] why not use relative refs in HTML output?
Date: Mon, 21 Apr 2003 16:28:15 -0400

=================== BUG #3296: FULL BUG SNAPSHOT ===================
http://savannah.nongnu.org/bugs/?func=detailbug&bug_id=3296&group_id=1409

Submitted by: kisch                   Project: mldonkey, a free e-Donkey client
Submitted on: Mon 04/21/2003 at 20:28
Category:  HTTP interface             Severity:  5 - Major                  
Bug Group:  None                      Resolution:  None                     
Assigned to:  None                    Status:  Open                         
Release:  None                        Release:  2.04rc1-0                   
Platform Version:  Linux i386-i686    Binaries Origin:  Downloaded from Savannah

Summary:  [enhancement] why not use relative refs in HTML output? 

Original Submission:  Hello, thanks for your great work!

Using relative refs in the generated HTML would enhance the possibilities to 
embed the mldonkey web interface into a larger apache setup.

If relative refs were used, a single apache ProxyPass directive would be 
sufficient to access the mldonkey web interface. As it is, the start frame 
contains requests to path-absolute URLs like e.g. /commands.html, so the 
following HTTP requests all need separate rewrite rules on their own.

And because the web browser assembles complete, absolute paths for the HTTP 
requests anyway from any relative path it sees in HTML, you wouldn't even have 
to change the HTTP request parsing code. Just drop the leading slashes from the 
output ;-)




No Followups Have Been Posted


CC list is empty


No files currently attached


For detailed info, follow this link:
http://savannah.nongnu.org/bugs/?func=detailbug&bug_id=3296&group_id=1409




reply via email to

[Prev in Thread] Current Thread [Next in Thread]