[OGo-Developer] Bugs in mod_ngobjweb

[Helge Hess]

On 27.03.2008, at 09:49, St=E9phane Corth=E9sy wrote:
> Does this mean that mod_ngobjweb does not support file upload?

Sure it does (and its used that way a lot in OGo, not exactly sure why =20=

you are experiencing issues).

> I know very little about apache, bear with me.
> Currently I have this config:

Hm, no, you either use mod_ngobjweb OR mod_proxy :-)


OK, back to the start ;-) What is mod_ngobjweb. Its
a) a non-streaming proxy
b) a protocol downgrader
c) a load balancer which works in combination with snsd
You usually don't care about c).

a) means that mod_ngobjweb collects the whole HTTP requests sent by =20
the browser before it transfers it to the SOPE application. This =20
removes the browser<->WAN<->Server latency/slowness towards the app. =20
Which is important because the SOPE app is non-threaded (and doesn't =20
use non-blocking-IO for reading requests), hence it should not block =20
on IO.

b) is basically the reason why you could not use Apache mod_proxy as a =20=

SOPE frontend, even if you don't care about issue a). SOPE =20
applications are not fully conforming HTTP servers, especially not =20
HTTP/1.1 ones. Therefore Apache is used in front, which does all the =20
HTTP heavy-lifting. mod_ngobjweb then talks HTTP/1.0 w/o keepalive etc =20=

to the SOPE app.
Now the new thing (and that was my comment in the last mail) is, that =20=

mod_proxy can now also do the downgrade for 'b0rked' HTTP backend =20
servers.

Why would you want to use mod_proxy. Well, it comes preinstalled with =20=

every Apache and its of course much more stable :-)
Not sure yet how to resolve a) though.


Summary for you: you probably want to ignore all that and continue =20
fixing your specific mod_ngobjweb problem :-)

Greets,
   Helge
--=20
Helge Hess
http://www.helgehess.eu/=