Hi! So (having a little editing issue with the ampersands...)

wconnect/Page1.awp?param1=value

is working fine.

But if there's an ampersand at the beginning of the query string, i.e.,:

wconnect/Page1.awp?&param1=value

WWWC seems to think it's coming from another extension, specifically, "awp2".

In the browser, in the address bar, it's "Page1.awp".

In the wwrequestlog it is clearly showing as "Page1.awp2".

Here's what's in the web.config that looks relevant. I'm sure it's just a config thing not right somewhere.

    <handlers>
      <add name="Aceweb" path="*.awp" verb="*" type="Westwind.WebConnection.WebConnectionHandler" resourceType="Unspecified" requireAccess="Script" preCondition="integratedMode" />
      <add name="AWP2" path="*.awp2" verb="*" type="Westwind.WebConnection.WebConnectionHandler" resourceType="Unspecified" requireAccess="Script" preCondition="integratedMode" />
      <add name="AWP3" path="*.awp3" verb="*" type="Westwind.WebConnection.WebConnectionHandler" resourceType="Unspecified" requireAccess="Script" preCondition="integratedMode" />
      <add name="WCScript" path="*.wcs" verb="*" type="Westwind.WebConnection.WebConnectionHandler" resourceType="Unspecified" requireAccess="Script" preCondition="integratedMode" />
      <add name="WCPage" path="*.wc" verb="*" type="Westwind.WebConnection.WebConnectionHandler" resourceType="Unspecified" requireAccess="Script" preCondition="integratedMode" />
    </handlers>

Thanks for any pointers!

Probably could use some more info:

Web Connection Handler 8.1.2 (.NET Handler)

Also, this doesn't seem to be the case on all pages. Just this one particular one. I'm thinking some kind of URL rule in IIS. I haven't been able to connect to that client's server directly yet. Just preparing for when I can.

Check in the Web Connection log and see what the actual incoming URL is. If it shows the .awp2 extension then it's something that's happening in IIS. If it's not then there's a parsing issue, but I find that hard to believe - not sure how an .awp extension could morph into a .awp2 extension.

One thing to check:

Web Connection uses SET EXACT OFF by default so if you're checking for the extension perhaps make sure you're forcing and exact match via == or similar.

+++ Rick ---

Thanks for the tips.

I got connected with their IT folks, and saw the wrong extension in the WC logs, and the IIS logs, and tracked it down a rule in their F5 load balancer to redirect to the wrong extension.

Go figure. They guessed it was put there last decade sometime for migration purposes.