Andreas Flack pisze:

Hi!

> So I'm not sure if this is a known problem or not (I seem to remember
> that some issue with alias directives existed in 1.6 or so), but it
> seems it wasn't caused by my update to 1.8.6. Sorry for all the trouble!

Yes, Alias directive is still an issue.
It can not be fixed without module refactoring.
You can read proposal at dev list.
http://www.midgard-project.org/discussion/developer-forum/fwd--midgard-user--wet_dog-compilation_issues_on_osx/


> BTW: Disabling MidgardEngine for the static directory seems like a nice
> idea even outside of debugging. 

Yes, very good point. I already added it to default configuration.

> This will of course fail, resulting first in a MidCOM run and
> then in a 404 error. If MidgardEngine was disabled in the static dir by
> default, we could at least skip the MidCOM run before delivering the 404
> error.

MiDCOM is not invoked at this point. We waste time to find host, page
and build argv/argc arrays. But every milisecond counts.

So, to sum up. You do not have any segfaults/sigaborts any longer?

Piotras


_______________________________________________
user mailing list
[email protected]
http://lists.midgard-project.org/mailman/listinfo/user

Reply via email to