...I need to learn how to hit "reply list" instead of "reply."

No, it just doesn't work for me... you'll see in my example that I had 
[P] on my RewriteRule, too.  I even tried copying your configuration 
exactly, but it didn't work.  It still shows the response headers in the 
browser.

If I inspect the response headers that were actually interpreted by the 
browser, I get:

HTTP/1.1 200 OK
Date: Thu, 30 Dec 2010 21:43:45 GMT
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Transfer-Encoding: chunked
Content-Type: text/plain

As opposed to the headers printed on the page (reposted here for 
purposes of comparison):

HTTP/1.1 1 -Date: Thu, 30 Dec 2010 21:43:45 GMT
Server: Tntnet/2.0
Content-Length: 148
Content-Type: text/html; charset=UTF-8
Keep-Alive: timeout=15000, max=999
Connection: Keep-Alive

As you can see above, I even updated tntnet to version 2.0 and I'm still 
getting the same result... which makes me think it's something to do 
with my apache configuration.  Any ideas?

Perhaps I should post this on an apache list instead of here?

On 12/29/2010 1:33 PM, Tommi Mäkitalo wrote:
> Hi,
>
> I don't really know, why your configuration works so strange but I have done 
> it
> before without problems.
>
> I use RewriteRules for that. I just tried this on my local apache:
>
>       RewriteEngine on
>       RewriteRule ^/tntnet/(.*)$ http://127.0.0.1:8000/$1  [P]
>
> With this I can access my tntnet server on port 8000 using
> http://localhost/tntnet/something.
>
> The last [P] tells apache to do an internal proxying instead of an external
> redirect.
>
> Hope that helps.
>
>
> Tommi
>
>
> Am Mittwoch, Dezember 29, 2010, 14:47:07 schrieb Shadowcat:
>>    Hello,
>>
>> I run a server with several websites on it, most of which use apache to
>> serve them.  I'm trying to get tntnet to work on this server as a
>> subdomain passed through a proxy - i.e., instead of having to access
>> myserver.com:8080, I want users to be able to access tntnet through
>> tntnet.myserver.com.
>>
>> After some looking, I found mod_proxy and mod_rewrite.  I've tried two
>> different methods here, but both of them end up working the same:
>>
>> <VirtualHost *:80>
>> ServerName tntnet.myserver.com
>>
>> ProxyPass               /       http://localhost:8080/
>> ProxyPassReverse        /       http://localhost:8080/
>> <proxy *>
>> Order allow,deny
>> Allow from all
>> </proxy>
>> </VirtualHost>
>>
>> and:
>>
>> <VirtualHost *:80>
>> ServerName tntnet.myserver.com
>>
>> RewriteRule /(.*) http://localhost:8080/$1
>> <proxy *>
>> Order allow,deny
>> Allow from all
>> </proxy>
>> </VirtualHost>
>>
>> Both of these work... except not really.  When I visit
>> tntnet.myserver.com, I do get the proper document, but instead of being
>> formatted as an html file as would be expected, it looks like this:
>>
>> HTTP/1.1 1 OKConnection: Keep-Alive
>> Content-Length: 148
>> Content-Type: text/html; charset=iso-8859-1
>> Date: Wed, 29 Dec 2010 13:40:30 GMT
>> Keep-Alive: timeout=15000, max=999
>> Server: Tntnet/1.6.3
>>
>>
>>
>> <html>
>> <head>
>> </head>
>> <body>
>> Test page
>> </body>
>> </html>
>>
>> Anyone have any ideas how to make this work?  I'm guessing tntnet is
>> sending the headers to Apache rather than to the browser, anyone know
>> how to fix that?
>>
>> ---------------------------------------------------------------------------
>> --- Learn how Oracle Real Application Clusters (RAC) One Node allows
>> customers to consolidate database storage, standardize their database
>> environment, and, should the need arise, upgrade to a full multi-node
>> Oracle RAC database without downtime or disruption
>> http://p.sf.net/sfu/oracle-sfdevnl
>> _______________________________________________
>> Tntnet-general mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/tntnet-general
>
> ------------------------------------------------------------------------------
> Learn how Oracle Real Application Clusters (RAC) One Node allows customers
> to consolidate database storage, standardize their database environment, and,
> should the need arise, upgrade to a full multi-node Oracle RAC database
> without downtime or disruption
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Tntnet-general mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/tntnet-general

------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and, 
should the need arise, upgrade to a full multi-node Oracle RAC database 
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Tntnet-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tntnet-general

Reply via email to