Plone 5: sometimes response mime_type is text/plain

[keul]

How to reproduce:

• create a new Plone site
• install PFG
• create a new form

On my environment the first attempt to create a PFG on a new site will show the HTML source (not interpreted) on the browser. By debugging the server response I see that the mime is text/plain.

I reproduced this issue on normal Plone usage but also on automated browser tests (see collective/uwosh.pfg.d2c#23)

No bloody idea of what cause this... maybe is only in development? Is Diazo?

[cdw9]

We are also seeing this happen on a client instance, Plone 5.0.7. It's not only happening in development. It tends to only happen when you first visit the form, it goes back to normal after a refresh.

I've also seen the mime time set to "application/javascript" when the HTML displays.

I haven't tried fixing the edit form, but the view seems to be fixed by changing the default_view, immediate_view and view_methods to use fg_base_view_p3 instead of the view alias.

[mauritsvanrees]

Confirmed on Plone 5.0 for the first form that you try to create. No idea currently.

[cdw9]

My fix above does not actually work, but I did find this:

I put a PDB into fgMaybeForceSSL. This function is hit twice. The first time, self.REQUEST.response.listHeaders() show the correct type. The second time, it is set to 'application/javascript'. I don't know what changes in the middle, but adding self.REQUEST.response.addHeader('Content-Type', 'text/html') here forces it to the correct type.

[cdw9]

But even with the correct type, the page renders without the Diazo theme...