Well, it's not really a nogap issue. It's a Xing header issue at its core. Once that is solved, it should be possible to reenable Xing headers on nogap, but that's a bridge to be crossed later.

And I am trying to contact Robert Hegemann.