Fix iframe exclusion logic.

Open TheSeeker opened this issue 4 years ago • 4 comments

sendReplyHeadersFproxy() is for filtered content on freenet. sendReplyHeaders() is for toadlets like plugins. we were denying iframes for local toadlets while potentially allowing them for freesites - depending which overloaded method was called.

Jun 05 '21 22:06 TheSeeker

I am not sure about this one. We used to have plugins that Freesites could embed as iframes. Currently we do not have them, but they are a valid usecase for interactivity. The HTML-filter ensures that only Freenet- and fproxy-content can be in an iframe.

Oct 17 '21 09:10 ArneBab

Aren't the iframes in freesites used for NIMs?

Oct 17 '21 10:10 nextgens

I think currently not, but that is a usecase.

Nov 24 '21 21:11 ArneBab

@ArneBab @nextgens i am not sure than this use case chould block this PR in 2024.

May 06 '24 11:05 hernic