passing custom headers

Topics: Developer Forum, Project Management Forum, User Forum
Sep 9, 2010 at 1:26 PM
Edited Sep 9, 2010 at 1:29 PM

Hi, all.

I've been writing Open API services that use HTTP header as service parameter.

And I use Windows 2003 Server, IIS 6.

Also I've installed IIRF successfully.

But I have a problem.

See the following...

--------------------------------------------------------------------

HTTP Request

GET http://168.219.186.100/OpenAPI/Service/CERM/System/message HTTP/1.1
Connection: Keep-Alive Keep-alive
If-Modified-Since: 2010-09-09 오후 8:00:52
ServiceID: test
Token: 91633c87+test+cc533bbbb0fd155458a05aabc84ff41b4
Host: 168.219.186.100
Connection: Keep-Alive

---------------------------------------------------------------------------

iirf.ini

ProxyPass ^/(openapi/service/cerm/.*)$  http://168.219.187.106:25231/$1 [I]

-----------------------------------------------------------------------------------

As you can see above, I use the custom headers such as "ServiceID","Token" etc. in HTTP Request.

I  try to rewrite "port" from 80 to 25231 using ProxyPass directive.

Now, ProxyPass directive operate correctly except that my custom header isn't passed to new URI(http://168.219.187.106:25231/$1)

I want to pass my custom headers to new URI.

anyone has a solution?

plz give me a solution...

thanks.

Coordinator
Sep 10, 2010 at 2:01 PM
You must be using the latest v2.1 iirf to get proper handling of headers across proxied requests. Also, is it ok to simply define new headers in the http request? according to my reading of rfc2616, you must use x- prefix, on custom optional headers, to distinguish them from the standard ones. You may want to double check that. This shouldn't affect iirf operation, though. It will forward even unknown headers in proxies requests.