ProxyPass

Jan 11, 2010 at 9:17 PM

Hi,

using IIRF.ini

StatusUrl /iirfStatus
RewriteLog  c:\temp\iirfLog.out
RewriteLogLevel 2
RewriteEngine ON
ProxyPass /http-bind/ http://localhost:7070/http-bind/

Sending : http://localhost/http-bind/

the log files shows:

Mon Jan 11 23:10:25 -   236 - DoRewrites: Url (no decoding): '/http-bind/'
Mon Jan 11 23:10:25 -   236 - DoRewrites: Proxy to: 'http://localhost:7070/http-bind/'
Mon Jan 11 23:10:25 -   236 - DoRewrites: requires rewrite to: '/proxy.iirf?path=/LM/W3SVC/1/ROOT&url=http://localhost:7070/http-bind/'

What is the meaning of the 3rd line? Does the rewrite happen ?

Thanks

 

 

 

Coordinator
Jan 11, 2010 at 10:16 PM
Edited Jan 11, 2010 at 10:18 PM

The third line reflects the design of IIRF, and ISAPI, which dictates that proxying a request requires a rewrite, internally. This is because IIRF is structured as an ISAPI Filter, but ISAPI Filters cannot behave as proxies.  Therefore the request needs to be rewritten to a URL that will be received again by IIRF, but this time acting as an ISAPI Extension. The ISAPI Extension can behave as a proxy.

You will have needed to configure IIRF as an ISAPI Extension in order to get the proxying to work, as described in the doc.  Did you do that?

As for "did the rewrite happen"?  I don't know. Is there anything else in the log?  Does your IIS log indicate that a request to proxy.iirf was received and handled?

 

Jan 12, 2010 at 3:02 AM
ooppsss..... forgot about the extension.... that did the trick!

Thanks!!!


2010/1/12 Cheeso <notifications@codeplex.com>

From: Cheeso

The third line reflects the design of IIRF, and ISAPI, which dictates that a proxy requires a rewrite, internally.

The request is being rewritten to a URL that will be received again by IIRF, but this time acting as an ISAPI Extension. 

You will have needed to configure IIRF as an extension in order to get the proxying to work.  Did you do that?

As for "did the rewrite happen"?  I don't know. Is there anything else in the log?  Does your IIS log indicate that a request to proxy.iirf was received and handled?

 

Read the full discussion online.

To add a post to this discussion, reply to this email (IIRF@discussions.codeplex.com)

To start a new discussion for this project, email IIRF@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on CodePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at CodePlex.com


Jan 12, 2010 at 4:17 AM

Hi,

Our requirement is very simple, to publish a complete application running on Apache port 8080 through IIS running on port 80, same machine.

The following IIRF rule seems to the the work:

RewriteEngine ON

 

RewriteLog  c:\temp\I2RFLog.out

RewriteLogLevel 3

ProxyPass ^/(.*)$ http://consisweb:8080/$1

Acording with Apache log:

 

68.168.223.202 - - [11/Jan/2010:23:12:51 -0800] "GET /sysworkflow/en/consis/login/login HTTP/1.1" 200 2994
68.168.223.202 - - [11/Jan/2010:23:12:51 -0800] "GET /jscore/labels/en.js HTTP/1.1" 200 8518
68.168.223.202 - - [11/Jan/2010:23:12:51 -0800] "GET /skins/green/style.css HTTP/1.1" 200 45630
68.168.223.202 - - [11/Jan/2010:23:12:51 -0800] "GET /jsform//login/login.js HTTP/1.1" 200 3733
68.168.223.202 - - [11/Jan/2010:23:12:51 -0800] "GET /js/widgets/calendar/pmcalendar.js HTTP/1.1" 200 87258
68.168.223.202 - - [11/Jan/2010:23:12:51 -0800] "GET /js/widgets/jscalendar/lang/calendar-en.js HTTP/1.1" 200 3804
68.168.223.202 - - [11/Jan/2010:23:12:51 -0800] "GET /js/maborak/core/maborak.js HTTP/1.1" 200 258771
68.168.223.202 - - [11/Jan/2010:23:12:51 -0800] "GET /jscore/labels/en.js HTTP/1.1" 200 8518
68.168.223.202 - - [11/Jan/2010:23:12:51 -0800] "GET /js/widgets/calendar/pmcalendar.js HTTP/1.1" 200 87258
68.168.223.202 - - [11/Jan/2010:23:12:51 -0800] "GET /images/consis.logo.jpg HTTP/1.1" 200 8485
68.168.223.202 - - [11/Jan/2010:23:12:51 -0800] "GET /images/PowerdbyProcessMaker.png HTTP/1.1" 200 9388

 [11/Jan/2010:23:12:51 -0800] "GET /sysworkflow/en/consis/login/login HTTP/1.1" 200 2994

 [11/Jan/2010:23:12:51 -0800] "GET /jscore/labels/en.js HTTP/1.1" 200 8518

 [11/Jan/2010:23:12:51 -0800] "GET /skins/green/style.css HTTP/1.1" 200 45630

 [11/Jan/2010:23:12:51 -0800] "GET /jsform//login/login.js HTTP/1.1" 200 3733

 [11/Jan/2010:23:12:51 -0800] "GET /js/widgets/calendar/pmcalendar.js HTTP/1.1" 200 87258

 [11/Jan/2010:23:12:51 -0800] "GET /js/widgets/jscalendar/lang/calendar-en.js HTTP/1.1" 200 3804

 [11/Jan/2010:23:12:51 -0800] "GET /js/maborak/core/maborak.js HTTP/1.1" 200 258771

 [11/Jan/2010:23:12:51 -0800] "GET /jscore/labels/en.js HTTP/1.1" 200 8518

 [11/Jan/2010:23:12:51 -0800] "GET /js/widgets/calendar/pmcalendar.js HTTP/1.1" 200 87258

 [11/Jan/2010:23:12:51 -0800] "GET /images/consis.logo.jpg HTTP/1.1" 200 8485

 [11/Jan/2010:23:12:51 -0800] "GET /images/PowerdbyProcessMaker.png HTTP/1.1" 200 9388

Things look good, but just the login page structure loads well, CSSs, images and scripts are missing.

When posting usr and pass, is not registered in Apache an error 404 arrives.

 

Any ideas?

Regards