> Hi Saransh, > > sorry, but my first question may not have been clear or I maybe > misunderstanding you: > If you installed Bloodhound on your server, what is the URL you use to access > this installation? > > Also in the mail below you state that you cannot access Bloodhound via > http://localhost:8080/bloodhound/. How did you try this? Did you use the > "wget" utility? > > When you are logged in to your server via SSH and you cannot access > bloodhound via http://localhost:8080/bloodhound/, how should Apache access > bloodhound via this URL? > 1. First of all you need to make sure you have the correct URL to access > bloodhounds webUI. > 2. When you have this URL, assure that you can access it via wget from a > console on the server on which Apache HTTPd is running > 3. Configure Apache HTTPd's mod_proxy to redirect to this URL > > Please let us know your findings. > > Regards > Alex > > Am 16.06.2013 um 21:59 schrieb Saransh Sharma <[email protected]>: > >> This is my apache conf for bloodhound >> >> ProxyRequests Off >> ProxyPass /bloodhound http://localhost:8080/bloodhound >> ProxyPassReverse /bloodhound http://localhost:8080/bloodhound >> >> <Proxy *> >> Order Deny,Allow >> Allow from all >> </Proxy> >> >> >> and domain is upscale.in:8080/bloodhound >> >> once i will add this neither it will work on upscale.in/bloodhound nor on >> port 8080 >> >> >> There is a error log file attached to the email >> >> error.log is for apache >> trac.log is for bloodhound... >> >> Upscale Server is Ubuntu Based virtual server on of our own infra which has >> xen server >> >> this server has 2gb ram and ubuntu 12.04 running on it and 20 gb of hdd with >> ssl installed on >> >> Anything you guys might need just inform me asap >> >> Thanks for the support you guys are doing !! >> >> >> On Mon, Jun 17, 2013 at 1:13 AM, Maek Twain <[email protected]> wrote: >> Hi Saransh, >> >> at least for me there are multiple open questions. >> >> 1. What is the exact direct URL of your bloodhound installation? >> In one of the last mails you posted the following part of your >> mod_proxy configuration >> > ProxyRequests Off >> > ProxyPass /volleyvz http://localhost:8080/volleyvz/ >> > ProxyPassReverse /volleyvz http://localhost:8080/volleyvz/ >> >> Yeah these are sample urls but they are very similar i have double >> checked them. >> >> They are as http://localhost:8080/blodhound >> >> But the error message below mentions a URL like >> > http://upscale.in/bloodhound >> >> Yes this is a public domain where i am looking to access it you can try >> it >> >> >> 2. Assuming that the direct URL of your bloodhound installation is >> http://upscale.in:8080/bloodhound/, can you access this bloodhound >> installation >> 2.1 from your browser without any problems? >> 2.2 from your server e.g. via "wget http://localhost:8080/bloodhound/? >> >> >> Yeah when there is,no proxy configuration ...in apache...but with >> apache proxy configs......nopes its not even working on port 8080 >> >> Some additional notes: >> a) Take care of trailing slashes in your mod_proxy configuration >> You will note that there is a significant difference between >> ProxyPass /bloodhound http://localhost:8080/bloodhound/ >> and >> ProxyPass /bloodhound http://localhost:8080/bloodhound >> You should test and take care of this. >> >> I haven't tried it let me do this >> >> b) In your above example it seems that bloodhound is running on the >> same host as you Apache HTTPd. In this case you probably don't need >> the "ProxyPassReverse" setting as the only purpose of this is to >> rewrite the domain in the response's header fields. It doesn't rewrite >> domain names e.g. in the HTML of the response. You'd need >> mod_proxy_html if you really want to do that. >> https://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxypassreverse >> >>>>> >> Ok let me look at it >> >> >>>>>>> >> c) You might want to use "ProxyPreserveHost=On" >> You can check on the meaning of this setting here: >> https://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxypreservehost >> >> >> Could you please attach the complete request (including HTTP-Headers) >> you send from your browser to http://upscale.in/bloodhound/ (if this is >> the correct URL) and the complete configuration of? >> >>>>>>>>>€> >> >> Sure >> >> >> Regards >> Alex >> >> Best Regards >> >> Saransh Sharma >> Sent from Windows Phone >> >> >> Upscale Consultancy Services PVT LTD. >> >> Disclaimer: >> >> ---------------------------------------------------------------------------------------------- >> This email was sent from within the Upscale Consultancy Services Pvt >> Ltd. The contents of this email, including the attachments, are LEGALLY >> PRIVILEGED AND CONFIDENTIAL to the intended recipient at the email >> address to which it has been addressed. If you receive it in error, >> please notify the sender immediately by return email and then >> permanently delete it from your system.The unauthorized use, >> distribution, copying or alteration of this email, including the >> attachments, is strictly forbidden. Thank you.Please note that neither >> Upscale Group nor the sender accepts any responsibility for viruses and >> it is your responsibility to scan the email and attachments (if any). >> ---------------------------------------------------------------------------------------------- >> From: Alexander Heusingfeld >> Sent: 17-06-2013 00:44 >> To: [email protected] >> Cc: Ryan Ollos >> Subject: Re: Httpd install on port :80 WAS: [GSoC] IRequestHandler >> question regarding the embedding of objects on external websites >> Hi Saransh, >> >> at least for me there are multiple open questions. >> >> 1. What is the exact direct URL of your bloodhound installation? >> In one of the last mails you posted the following part of your >> mod_proxy configuration >> > ProxyRequests Off >> > ProxyPass /volleyvz http://localhost:8080/volleyvz/ >> > ProxyPassReverse /volleyvz http://localhost:8080/volleyvz/ >> >> But the error message below mentions a URL like >> > http://upscale.in/bloodhound >> >> >> 2. Assuming that the direct URL of your bloodhound installation is >> http://upscale.in:8080/bloodhound/, can you access this bloodhound >> installation >> 2.1 from your browser without any problems? >> 2.2 from your server e.g. via "wget http://localhost:8080/bloodhound/? >> >> >> Some additional notes: >> a) Take care of trailing slashes in your mod_proxy configuration >> You will note that there is a significant difference between >> ProxyPass /bloodhound http://localhost:8080/bloodhound/ >> and >> ProxyPass /bloodhound http://localhost:8080/bloodhound >> You should test and take care of this. >> >> b) In your above example it seems that bloodhound is running on the >> same host as you Apache HTTPd. In this case you probably don't need >> the "ProxyPassReverse" setting as the only purpose of this is to >> rewrite the domain in the response's header fields. It doesn't rewrite >> domain names e.g. in the HTML of the response. You'd need >> mod_proxy_html if you really want to do that. >> https://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxypassreverse >> >> c) You might want to use "ProxyPreserveHost=On" >> You can check on the meaning of this setting here: >> https://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxypreservehost >> >> >> Could you please attach the complete request (including HTTP-Headers) >> you send from your browser to http://upscale.in/bloodhound/ (if this >> is the correct URL) and the complete configuration of? >> >> Regards >> Alex >> >> >> Am 16.06.2013 um 19:02 schrieb Saransh Sharma <[email protected]>: >> >> > Proxy Error >> > >> > The proxy server received an invalid response from an upstream server. >> > The proxy server could not handle the request *GET >> > /bloodhound<http://upscale.in/bloodhound> >> > *. >> > >> > Reason: *Error reading from remote server* >> > ------------------------------ >> > Apache/2.2.22 (Ubuntu) Server at upscale.in Port 80 >> > >> > >> > On Sun, Jun 16, 2013 at 3:43 PM, Saransh Sharma >> > <[email protected]>wrote: >> > >> >> Oops i think i did not set this bld/ logign ...now i did that ...after >> >> that i am gonna do that mod_proxy for apache then i will see the logs and >> >> let you know asap!!! >> >> >> >> >> >> Thanks >> >> >> >> >> >> On Sun, Jun 16, 2013 at 3:29 AM, Maek Twain <[email protected]> wrote: >> >> >> >>> Yeah,i on it >> >>> >> >>> Best Regards >> >>> >> >>> Saransh Sharma >> >>> Sent from Windows Phone >> >>> >> >>> >> >>> Upscale Consultancy Services PVT LTD. >> >>> >> >>> Disclaimer: >> >>> >> >>> >> >>> ---------------------------------------------------------------------------------------------- >> >>> This email was sent from within the Upscale Consultancy Services Pvt >> >>> Ltd. The contents of this email, including the attachments, are LEGALLY >> >>> PRIVILEGED AND CONFIDENTIAL to the intended recipient at the email >> >>> address to which it has been addressed. If you receive it in error, >> >>> please notify the sender immediately by return email and then >> >>> permanently delete it from your system.The unauthorized use, >> >>> distribution, copying or alteration of this email, including the >> >>> attachments, is strictly forbidden. Thank you.Please note that neither >> >>> Upscale Group nor the sender accepts any responsibility for viruses and >> >>> it is your responsibility to scan the email and attachments (if any). >> >>> >> >>> ---------------------------------------------------------------------------------------------- >> >>> From: Ryan Ollos >> >>> Sent: 16-06-2013 03:15 >> >>> To: [email protected] >> >>> Subject: Re: Httpd install on port :80 WAS: [GSoC] IRequestHandler >> >>> question regarding the embedding of objects on external websites >> >>> On Sat, Jun 15, 2013 at 11:54 AM, Olemis Lang <[email protected]> wrote: >> >>> >> >>>> On 6/15/13, Saransh Sharma <[email protected]> wrote: >> >>>>> Hey these are the errors when i was using reverse proxy >> >>>>> >> >>>>> r] server reached MaxClients setting, consider raising the MaxClients >> >>>>> setting >> >>>>> [Fri Jun 14 07:59:40 2013] [error] [client 10.2.195.15] (70007)The >> >>>> timeout >> >>>>> specified has expired: proxy: error reading status line from remote >> >>>> server >> >>>>> localhost:8080 >> >>>> >> >>>> These are log entries for proxy activity , not Bloodhound . >> >>>> >> >>>> Does localhost:8080 *respective to the target proxy server* really work >> >>> ? >> >>>> If not, please let us know of the relevant entries logged in >> >>>> /path/to/bh/env/log/trac.log (... after enabling logging e.g. via >> >>>> logging admin panel) >> >>>> >> >>>> PS: /path/to/bh/env above is a dummy placeholder >> >>>> >> >>>> [...] >> >>>> >> >>>> -- >> >>>> Regards, >> >>>> >> >>>> Olemis. >> >>>> >> >>> >> >>> In addition to what Olemis suggested, we'd like to see the configuration >> >>> directives you've used. Please post those files here. >> >>> http://httpd.apache.org/docs/2.2/mod/mod_proxy.html >> >>> >> >>> I've never setup mod_proxy, but am willing to experiment with it if you >> >>> provide enough information on how you go to where you are now. >> >>> >> >> >> >> >> >> >> >> -- >> >> >> >> Best Regards >> >> >> >> Saransh Sharma >> >> >> >> Upscale Consultancy PVT LTD. >> >> >> >> Disclaimer: >> >> >> >> >> >> ---------------------------------------------------------------------------------------------- >> >> This email was sent from within the Upscale Consultancy Services Pvt Ltd. >> >> The contents of this email, including the attachments, are LEGALLY >> >> PRIVILEGED AND CONFIDENTIAL to the intended recipient at the email address >> >> to which it has been addressed. If you receive it in error, please notify >> >> the sender immediately by return email and then permanently delete it from >> >> your system.The unauthorized use, distribution, copying or alteration of >> >> this email, including the attachments, is strictly forbidden. Thank >> >> you.Please note that neither Upscale Group nor the sender accepts any >> >> responsibility for viruses and it is your responsibility to scan the email >> >> and attachments (if any). >> >> >> >> ---------------------------------------------------------------------------------------------- >> >> >> >> >> >> >> > >> > >> > >> > -- >> > >> > Best Regards >> > >> > Saransh Sharma >> > >> > Upscale Consultancy PVT LTD. >> > >> > Disclaimer: >> > >> > ---------------------------------------------------------------------------------------------- >> > This email was sent from within the Upscale Consultancy Services Pvt Ltd. >> > The contents of this email, including the attachments, are LEGALLY >> > PRIVILEGED AND CONFIDENTIAL to the intended recipient at the email address >> > to which it has been addressed. If you receive it in error, please notify >> > the sender immediately by return email and then permanently delete it from >> > your system.The unauthorized use, distribution, copying or alteration of >> > this email, including the attachments, is strictly forbidden. Thank >> > you.Please note that neither Upscale Group nor the sender accepts any >> > responsibility for viruses and it is your responsibility to scan the email >> > and attachments (if any). >> > ---------------------------------------------------------------------------------------------- >> >> >> >> -- >> Best Regards >> >> Saransh Sharma >> >> >> Upscale Consultancy PVT LTD. >> >> Disclaimer: >> >> ---------------------------------------------------------------------------------------------- >> This email was sent from within the Upscale Consultancy Services Pvt Ltd. >> The contents of this email, including the attachments, are LEGALLY >> PRIVILEGED AND CONFIDENTIAL to the intended recipient at the email address >> to which it has been addressed. If you receive it in error, please notify >> the sender immediately by return email and then permanently delete it from >> your system.The unauthorized use, distribution, copying or alteration of >> this email, including the attachments, is strictly forbidden. Thank >> you.Please note that neither Upscale Group nor the sender accepts any >> responsibility for viruses and it is your responsibility to scan the email >> and attachments (if any). >> ---------------------------------------------------------------------------------------------- >> >> >
signature.asc
Description: Message signed with OpenPGP using GPGMail
