There's two reasons (that i can think of) why they would send it as range request - first, to simply check if given server supports range or not. If this is the case, they also set method to HEAD so no content is served back (which also explains why your filter is not called). - second, they simply expect that og tags are in the head and they don't care about downloading whole page, so they use request to limit amount of data sent over ... and this is exactly why you would want to have range support enabled for html.
Anyway, I can't imagine how use of range filter would result in bypassing our filter. Are you sure it is not called? From the manipulation you do inside, I would more suspect that response gets committed before you get chance to intercept it. I probably write those tags in the output by other means, e.g. adding them directly during rendering as auto generated component/area or via modified htmlHeader or using modifystream-module module. -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=ee53194f-8bfc-45bb-afaf-57e7a9fc34f2 ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
