My understanding of the whole mapping process is

first step : the connectors checkes if there is a mapping fitting the 
request in jrun (for example *.jrun) and then forwards the request to it
second step : apache does its work =< rewritting rules
third step : if the rewritting rule is an external rewritting ([R] flag), 
it sends to itself the rewritted request, which then can be caught by the 
connector (return to step 1), and the response that will be received will 
be forwarded to the client. Else the rewritting rule is internal, and 
apache is likely to treat the request by himself (including cgi scripts, ...)
fourth step : the result is sent to the client browser

Could anybody confirm this ?

Is there any way to have the mapping executed by apache instead of itsself, 
or to call the connector from a rewritting rule (this should be possible, 
as long as it is possible to call any external program).
Is there a way to declare an application/x-form-??? mime-type jrun could 
intercept ? If not, then I don't understand why there is a mime type tab is 
jrun's administrator.
Would JRun 3 behave the same, by the way ?

I'd really like to have a response from Allaire techs about this subject.

Best regards
Sylvain




At 14:26 11/01/01 +0100, you wrote:


>   This concerns the way JRun 2.3.3 and Apache 1.3.12 interact.
>
>To those who are not very familiar with apache rewriting rule, here are
>some explainations
>The directive
>RewriteRule ^/torewrite\.html$ rewritted.html [R]
>causes a client's request for http://mysite/torewrite.html to be redirected
>to http://mysite/rewritted.html, and the location bar of the browser shows
>up the new url http://mysite/rewritted.html
>
>On the other hand, the directive
>RewriteRule ^/torewrite\.html$ rewritted.html
>(without [R] causes a client's request for http://mysite/torewrite.html to
>be redirected to http://mysite/rewritted.html, but the location bar of the
>browser still shows the old url http://mysite/torewrite.html
>
>As far as I  understood the documentation, the first case is called
>external rewritting, and is equivalent to another request to the rewritted 
>url.
>
>Sorry to have been that long, but here is my problem.
>
>One of the use of the rewritting rules is to emulate static documents when
>the real document is dynamic. This works well with cgi, for example.
>The fact is that spiders are not likely to reference dynamic sites, and do
>much better with static sites. So I would like to rewrite some generated
>pages to static names. ie
>RewriteRule ^/index\..html$ /aoServlet.jrun?param1=value1
>
>This works real fine with the [R] flag (first case above), but not at all
>without (second case). And so the problem is not solved, because what I
>wanted was to have index.html written on the client browser when the page
>that was loaded was generated by aoServlet.
>
>To my understanding, this is because the mapping to /servlet/ and to .jrun
>are done in jrun, and not in apache, but this is perhaps not that.
>
>Has anyone encountered and solved this problem ?
>If someyone out there that has a better understanding of how the jrun
>connector works could give me any clue of what's happening, I might find a
>solution by mylself
>
>Best regards
>
>
>
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to