Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Dispacter rendering the contents with mime type text/plain instead of text/html

Avatar

Level 2

Folks,

    I am having an issue where somehow when dispatcher serves the page contents from cache, it renders the plain html with the mime type of text/plain, however it should be rendering it as text/html. Not sure where and what is missing. This is what see in the dispatcher log.

Does anyone know what could I be missing? Another site hosted by the same dispatcher is rendering the pages correctly with mime type text/html

Thu Dec 19 22:46:17 2013] [D] [13653(47771052389216)] Found farm <MY_FORM> for <host>
[Thu Dec 19 22:46:17 2013] [D] [13653(47771052389216)] checking [/path/page.html]
[Thu Dec 19 22:46:17 2013] [D] [13653(47771052389216)] never flushed [/cache_folder/.stat] -> use cache [/cache_folder/path/page.html]
[Thu Dec 19 22:46:17 2013] [D] [13653(47771052389216)] cache-action for [path/page.html]: SPOOL
[Thu Dec 19 22:46:17 2013] [D] [13653(47771052389216)] request declined
[Thu Dec 19 22:46:17 2013] [I] [13653(47771052389216)] "GET /path/page.html" 200 - 0ms

1 Accepted Solution

Avatar

Correct answer by
Level 2

Hello Yogesh,

    I found that it was because of the virtual host mismatch. In the access log we were getting a different virtual host as compare to what we had in httpd.conf file. After fixing the issue, we started getting the contents correctly.

View solution in original post

2 Replies

Avatar

Level 5

Hello,

Check your mime_type file and make sure that for html you have added correct Mime Type. Some time it is in httpd.conf as well. Can you also check if publisher is returning correct Mime type ?

Yogesh

Avatar

Correct answer by
Level 2

Hello Yogesh,

    I found that it was because of the virtual host mismatch. In the access log we were getting a different virtual host as compare to what we had in httpd.conf file. After fixing the issue, we started getting the contents correctly.