Hi David, Well I used Adobe Flashbuilder now to write files to the server 
(verified by looking at their time stamps) and then looked into the 
/etc/httpd/logs/access_log file, and there's no activity reported there for 
this event. The last few entries were as follows (again, not related to Adobe):

127.0.0.1 - - [17/Feb/2012:08:45:01 -0800] "GET /whm-server-status HTTP/1.0" 
200 8978 
xx.xx.x.58 - - [17/Feb/2012:08:46:06 -0800] "GET / HTTP/1.0" 200 111 
127.0.0.1 - - [17/Feb/2012:08:46:06 -0800] "GET / HTTP/1.0" 200 111 

Also, I've tried endless entries into the URL input field for Abobe's software, 
such as

xx.xxx.xxx.196
mydomain.com
www.mydomain.com
mydomain.com:80
and so on...

I'm starting to think such settings may be making a difference, although 
mod_jk.log always reports host3.mydomain.com, so I'm just speculating.


----- Original Message ----- 
From: "David N. Smith" <david.sm...@cornell.edu> 
To: "Tomcat Users List" <users@tomcat.apache.org> 
Sent: Friday, February 17, 2012 8:43:57 AM 
Subject: Re: mod_jk doesn't map to software-generated web address, but maps to 
this address when I enter it into browser 


On Feb 17, 2012, at 10:27 AM, "André Warnier" <a...@ice-sa.com> wrote: 

> Christopher Schultz wrote: 
>> -----BEGIN PGP SIGNED MESSAGE----- 
>> Hash: SHA1 
>> To whom it may concern, 
>> On 2/16/12 1:29 PM, modjkl...@comcast.net wrote: 
>>> I took all JkMounts inside the VirtualHost tags and placed them outside 
>>> these tags, and above them added JkMountCopy All, 
>>> restarted Apache, and now Adobe successfully can access 
>>> mydomain.com/mywebapp. Thanks so much!!! 
>>> 
>>> I also tried modifying the above httpd.conf configuration by 
>>> removing the global JkMountCopy All line of code, and adding a 
>>> JkMountCopy On line of code inside the original VirtualHost tags, 
>>> but this also failed as before. Any idea why? 
>>> 
>>> Andre, I did worry about the "host3" designation initially, so I previously 
>>> added it to the VirtualHost tag here under ServerAlias: 
>>> 
>>> ServerAlias www.mydomain.com host3.mydomain.com 
>>> 
>>> So I assumed that should permit Adobe trying to access host3.mydomain.com 
>> I'm still curious as to why Adobe sees a different experience than you 
>> do with your web browser. 
> 
> Me too in fact. I didn't quite get Rainer's explanation, and still do not 
> understand why an Adobe request results in this URI being logged by mod_jk : 
> 
> [Thu Feb 16 06:47:35 2012] [13723:140020322740160] [debug] 
> jk_map_to_storage::mod_jk.c (3647): missing uri map for 
> host3.mydomain.com:/mywebapp/flex_wizard_project_test_script_server_550713325917236076.htm
>  
> 
> while when doing it by hand, the URI shown in the log is quite different : 
> 
> > [Thu Feb 16 06:55:21 2012] [13725:140020322740160] [debug] 
> > map_uri_to_worker_ext::jk_uri_worker_map.c (1036): Attempting to map URI 
> > '/mywebapp/flex_wizard_project_test_script_server_550713325917236076.htm' 
> > from 6 maps 
> 
> Is it just a variation due to how the mod_jk logging works, or is it really 
> that the request URI is arriving differently to Apache in one case or the 
> other ? 
> 
> Like : 
> - from a browser : 
> GET /mywebapp/flex_wizard_project_test_script_server_550713325917236076.htm 
> HTTP/1.1 
> Host: host3.mydomain.com 
> ... 
> 
> - from Adobe : 
> GET 
> host3.mydomain.com:/mywebapp/flex_wizard_project_test_script_server_550713325917236076.htm
>  HTTP/1.1 
> Host: ???? 
> ... 
> 
> ??? 
> 
> 

Partially to add to the chorus ... 

It *looks like* to my eye that Adobe is trying something strange like: 

http://host3.mydomain.com/host3.mydomain.com:/mywebapp/flex .... (the rest of 
the URL). 

Question is ... what happens if you don't specify the host ... just the server 
relative URL. Also the Apache httpd service should have access logs. What is 
listed there? 

FYI ... my access logs only show the part of the URL after the host/port. It's 
likely if you see host3.mydomain.com in there that Adobe is treating what you 
enter as a server relative URL instead of an absolute URL. 

--David 
--------------------------------------------------------------------- 
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org 
For additional commands, e-mail: users-h...@tomcat.apache.org 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to