We haven't really figured out what was that, but disabling rpaf helped, and then our sysadmin saw small missconfiguration of rpaf (that leaded on specific url that x-forwarded-for was not sent), turned it on again, but with a bit different config. Anyway we could not reproduce this bug in local environment, and it's gone in production, so let's consider it solved?
-- You received this message because you are subscribed to the Google Groups "modwsgi" group. To view this discussion on the web visit https://groups.google.com/d/msg/modwsgi/-/1BNKjUWKeakJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
