You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by "Sugimoto, Maroki" <Ma...@ca.com> on 2002/12/09 20:03:45 UTC

[users@httpd] non-ascii file names

Hi,

	Does anyone know how I can serve files with non-ascii file names?
	Are there any directives I can set in the CONF file?
	I am runing Apache2.x on SuSE 7.2.
	On other posts, I have read things like "HTTP protocol does not suport it" or "you have to encode it".
	But I have seen straight non-ascii file name work with Tomcat.
	So I figured if Tomcat can, why not Apache? Or was it the Java talking on Tomcat?

	Anyone, any ideas?

thanks


[users@httpd] apache-2.0.42, mod_proxy and mod_cache issues

Posted by Veselin Terzic <ve...@systems.dhl.com>.
non-ascii file namesdear apache users,

platform: linux red hat 7.2, apache 2.0.42 with mod_proxy and mod_cache

i use apache as a reverse proxy, i.e. using ProxyPass and ProxyPassReverse
to "accelerate" dozens of backend/web servers and different URLs.

scenario:

         (1)                             (2)
(3)                                             (4)
client----(internet)-->
SSL_termination_device--->apache-2.0.42_proxy_cache---->backend web servers

i have to maintain session persistency and i use "secure" cookies to achieve
that, but somehow sessions will get mixed up.
what is  exactly happening in the proxy engine and what is being cached that
can mix cookies up?

What is going to happen with HTTP/HTTPS traffic in the scenario above as it
pertains to RFC-2109 section 10.2 ?
Will mod_proxy pass cookie sent from the client to the server if the cookie
is "secure" and SSL is used only from the client to the SSL termination
engine (1-->2), but not from apache to the backend server?

Is apache-2.0.42 fully compliant with rfc-2616 and 2109?

Any help is greatly appreciated,
thanks
--veselin