Server requests: 302 followed by a 200

[Muffin]

Hi,

On an IIS system clicking a particular link the following response codes are returned:

GET /nl/nl/process?Someparameter1=1&Someparameter2=2

302 found

GET /nl/nl/SomeOtherPage.cms

200 OK

What concerns me, besides the obvious 302 and the cAmeLcAse canonical issues is the 200 response without a redirect.
What page will then be indexed, ranked and what effect does this have on the pagerank flow, if the 302 was to be changed into a 301?
Also would extention .cms be an issue?

Thanks for any answers.

Edit. I contacted the developer. He says it's a rewrite, not a meta redirect.
I still think, this rewrite is an issue? Canonical maybe?

[Muffin]

So why is the rewrite not an issue?
Google sees the GET /nl/nl/process?Someparameter1=1&Someparameter2=2, never mind the 302 (which is a very obvious issue).
Then it sees the GET /nl/nl/SomeOtherPage.cms
To Googlebot it might as well be a meta redirect, which is an issue, as this will not pass pagerank. Server response is not different from a meta redirect....

Or should I interprete the last GET in some other way?

I agree on the .cms

[eyepaq]

The rewrite is not an issue but you should change from 302 to 301 in order to pass the link equity to the new page.

As for the page name format, cms extension is not an issue from google's point of view. However from a user point of view that is not really friendly (not only the extension but the name in general). Since you can re-write the name as you want I would consider changing those into a more friendly look.

Hope it helps.

[AJPro]

IIS loves 302s... Ask your developer to change the 302 to a 301 instead.

The indexed page will then be  "/nl/nl/SomeOtherPage.cms" and the "link juice" will flow to it.

Also stick with lowercase in the urls.

The .cms extension is not an issue imo.