nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

LiveSite runtime error Page response code

Davinder

Hi,
I am using LiveSite 2.2.1 with Apache Tomcat 5.0 on the production server. In default.site i have mentioned my ErrorPage and that is getting displayed if the .page that user requests is not there, which is quite as expected.
The problem here is that the response header has status code as '200 OK' even when the page mentioned in ErrorPage is displayed to user, ideally the response code should be '404' as the page originally requested by user is not there.

Does anyone have any clue why liveSite runtime is behaving like this?

TIA,
Davinder

Find more posts tagged with

Comments

JoeHH

As your query has gone unanswered for so long, I am not encouraged that there is a clear solution.

We also are experiencing this issue.

Most content engines employing an error page also have some way to pass along the reason so you can act on it. Either the error page is just another view which is getting error info as it's model, or alternatively you are made to specify a different error page for each error code, and it will preserve a proper status code as it returns those pages.

Replying w/ a 200 error code in every case is not how a well behaved web application behaves, and presents specific challenges when it comes to spidering and the like.

I hope this is improved in future releases.

sanoboy

As your query has gone unanswered for so long, I am not encouraged that there is a clear solution.

We also are experiencing this issue.

Most content engines employing an error page also have some way to pass along the reason so you can act on it. Either the error page is just another view which is getting error info as it's model, or alternatively you are made to specify a different error page for each error code, and it will preserve a proper status code as it returns those pages.

Replying w/ a 200 error code in every case is not how a well behaved web application behaves, and presents specific challenges when it comes to spidering and the like.

I hope this is improved in future releases.

yes,i am now encounter the error page issue.i think it can not automatically link to the error page setted under default.site when link to a invalidate url.We should do some settings in some other place,(ex.like web.xml)but now i don't know where to set and how?anybody can give some advise?thx

AlexC

This is unfortunate behavior of 2.x products, I believe that for 3.1 this was fixed to return an error code.

tec_iwov

this has not yet been implemented. it is planned on going into the post 6.7.2 sp1 release.