[users@httpd] Issue with LDAPVerifyServerCert: On

[Roger Paanini]

Hi Folks,

I am having a problem connecting with LDAP when I turn on
LDAPVerifyServerCert. With this parameter turned off everything is working
fine.

I took tcpdump for both the scenarios. The only difference is in the list
of Distinquished Names that my LDAP server sends as part of the
"Certificate Request".

With LDAPVerifyServerCertificate turned on, I get a bunch of DNs in
Certificate Request. With it turned off, I get none.

In either case, the client (httpd) is getting the server certificate and
validating it.

Does anyone have any explanation for this behavior? I do not see any
downside to LDAPVerifyServerCert being turned off.

Any insights and comments?

Thanks!

Re: [users@httpd] Apache listening on UDP ports

[Marat Khalili]

Well, you can redirect UDP to TCP with tools like netcat. Not sure what you 
want to achieve, though. HTTP is mostly stream-oriented IMO.
-- 

With Best Regards,
Marat Khalili

On July 6, 2016 7:09:22 PM GMT+03:00, Hermes Moraes  
wrote:
>Dear all,
>
>   I'm wondering how to get Apache listening on TCP and UDP ports. I've
>found an option through Apache CXF framework but it seems to be quite
>complex (Web-Services, XML, etc.).
>   All I need is a simple HTTP server with one or two simple web pages
>answering requests on TCP or UDP ports. Any idea/direction?
>
>With best regards,
>Hermes.

Re: [users@httpd] Syntax checking an alternate configuration file

[Rich Bowen]

On 07/06/2016 12:17 PM, Darryl Philip Baker wrote:
> I want to syntax check an alternate configuration file in Apache 2.4 but
> I have hit a snag, “apachectl –t –f {full path name}” and “apachectl –f
> {full path name} configtest” give me an extra message which I don’t need
> and don’t want to see. I looked at the shell script that is apachectl
> and it looks like someone got lazy and if there is  a second argument it
> will always print the warning message. It may be a “feature” but it is a
> damn annoying one. Because I’m using RHEL I don’t want to just comment
> out the test in apachectl but I’m not sure it is a reportable bug. Opinions?

You should report this bug in Red Hat Bugilla, as that's where it's
likely to get addressed. Or possibly in Fedora Bugzilla, since that's
the upstream for the packages that land in RHEL. Or perhaps ask Joe
Orton directly. :-)

--Rich

> 
>  
> 
> [root@host build_conf]# apachectl -t -f /etc/httpd/build_conf/httpd.conf
> 
> Passing arguments to httpd using apachectl is no longer supported.
> 
> You can only start/stop/restart httpd using this script.
> 
> If you want to pass extra arguments to httpd, edit the
> 
> /etc/sysconfig/httpd config file.
> 
> httpd: “Here is the error message I am looking for”
> 
> [root@host build_conf]#
> 
>  
> 
> *Darryl Baker*
> 
> *Sr. System Administrator***
> 
> Distributed Application Platform Services (DAPS)
> 
> Project Management Office and Enabling Technologies (PMOET)
> 
> *Northwestern*| Information Technology(Formerly NUIT)
> 
> 1800 Sherman Ave., Suite 600
> 
> Evanston, IL  60201-3715
> 
> *(847) 467-6674*
> 
> www.it.northwestern.edu
> 
>  
> 


-- 
Rich Bowen - rbo...@rcbowen.com - @rbowen
http://apachecon.com/ - @apachecon

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

Re: [users@httpd] Syntax checking an alternate configuration file

[Yehuda Katz]

That is a change RedHat made to the script - it isn't in the regular
distribution.
RedHat explicitly discourages using a non-default-location configuration
file.

Ref: https://access.redhat.com/discussions/1605003

- Y

On Wed, Jul 6, 2016 at 12:17 PM, Darryl Philip Baker <
darryl.ba...@northwestern.edu> wrote:

> I want to syntax check an alternate configuration file in Apache 2.4 but I
> have hit a snag, “apachectl –t –f {full path name}” and “apachectl –f {full
> path name} configtest” give me an extra message which I don’t need and
> don’t want to see. I looked at the shell script that is apachectl and it
> looks like someone got lazy and if there is  a second argument it will
> always print the warning message. It may be a “feature” but it is a damn
> annoying one. Because I’m using RHEL I don’t want to just comment out the
> test in apachectl but I’m not sure it is a reportable bug. Opinions?
>
>
>
> [root@host build_conf]# apachectl -t -f /etc/httpd/build_conf/httpd.conf
>
> Passing arguments to httpd using apachectl is no longer supported.
>
> You can only start/stop/restart httpd using this script.
>
> If you want to pass extra arguments to httpd, edit the
>
> /etc/sysconfig/httpd config file.
>
> httpd: “Here is the error message I am looking for”
>
> [root@host build_conf]#
>
>
>
> *Darryl Baker*
>
> *Sr. System Administrator*
>
> Distributed Application Platform Services (DAPS)
>
> Project Management Office and Enabling Technologies (PMOET)
>
> *Northwestern* | Information Technology (Formerly NUIT)
>
> 1800 Sherman Ave., Suite 600
>
> Evanston, IL  60201-3715
>
> *(847) 467-6674 <%28847%29%20467-6674>*
>
> www.it.northwestern.edu
>
>
>

Re: [users@httpd] Apache listening on UDP ports

[Yehuda Katz]

HTTPD as currently released does not support listening on UDP ports.

A request like this came up in 2007 (
http://marc.info/?l=apache-httpd-users=118950412526067=2). At that
time, someone came up with patches to make it work, but those haven't been
maintained and there is no guarantee they would work now.

See: http://marc.info/?l=apache-httpd-dev=118899142517560=2

- Y


On Wed, Jul 6, 2016 at 12:09 PM, Hermes Moraes 
wrote:

> Dear all,
>
>I'm wondering how to get Apache listening on TCP and UDP ports. I've
> found an option through Apache CXF framework but it seems to be quite
> complex (Web-Services, XML, etc.).
>All I need is a simple HTTP server with one or two simple web pages
> answering requests on TCP or UDP ports. Any idea/direction?
>
> With best regards,
> Hermes.
>

[users@httpd] Syntax checking an alternate configuration file

[Darryl Philip Baker]

I want to syntax check an alternate configuration file in Apache 2.4 but I have 
hit a snag, "apachectl -t -f {full path name}" and "apachectl -f {full path 
name} configtest" give me an extra message which I don't need and don't want to 
see. I looked at the shell script that is apachectl and it looks like someone 
got lazy and if there is  a second argument it will always print the warning 
message. It may be a "feature" but it is a damn annoying one. Because I'm using 
RHEL I don't want to just comment out the test in apachectl but I'm not sure it 
is a reportable bug. Opinions?

[root@host build_conf]# apachectl -t -f /etc/httpd/build_conf/httpd.conf
Passing arguments to httpd using apachectl is no longer supported.
You can only start/stop/restart httpd using this script.
If you want to pass extra arguments to httpd, edit the
/etc/sysconfig/httpd config file.
httpd: "Here is the error message I am looking for"
[root@host build_conf]#

Darryl Baker
Sr. System Administrator
Distributed Application Platform Services (DAPS)
Project Management Office and Enabling Technologies (PMOET)
Northwestern | Information Technology (Formerly NUIT)
1800 Sherman Ave., Suite 600
Evanston, IL  60201-3715
(847) 467-6674
www.it.northwestern.edu

[users@httpd] Apache listening on UDP ports

[Hermes Moraes]

Dear all,

   I'm wondering how to get Apache listening on TCP and UDP ports. I've
found an option through Apache CXF framework but it seems to be quite
complex (Web-Services, XML, etc.).
   All I need is a simple HTTP server with one or two simple web pages
answering requests on TCP or UDP ports. Any idea/direction?

With best regards,
Hermes.

Re: [users@httpd] 403 Forbidden

[newlifeR REN]

Dear Eric,
First of all，thank you for attention to my issuse :)
Yes,I have updated httpd.conf file as Administrator and I uploaded the
error log and the
httpd.conf file

2016-07-06 18:35 GMT+08:00 Eric Covener :

> On Wed, Jul 6, 2016 at 4:13 AM, newlifeR REN  wrote:
> > I have installed wampserver(apache 2.4.18) on windows  when i access the
> > server on other pc and I have got en Error 403(you didn't have
> permission to
> > access on this server).I have changed the httpd.conf file following and I
> > also get the same error 403:
>
>
> What does your ErrorLog say?  Did you update your httpd.conf as
> Administrator?
>
> --
> Eric Covener
> cove...@gmail.com
>
> -
> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
> For additional commands, e-mail: users-h...@httpd.apache.org
>
>


apache_error.log
Description: Binary data


httpd.conf
Description: Binary data

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

Re: [users@httpd] 403 Forbidden

[Eric Covener]

On Wed, Jul 6, 2016 at 4:13 AM, newlifeR REN  wrote:
> I have installed wampserver(apache 2.4.18) on windows  when i access the
> server on other pc and I have got en Error 403(you didn't have permission to
> access on this server).I have changed the httpd.conf file following and I
> also get the same error 403:


What does your ErrorLog say?  Did you update your httpd.conf as Administrator?

-- 
Eric Covener
cove...@gmail.com

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

[users@httpd] 403 Forbidden

[newlifeR REN]

Hi bros,
I have installed wampserver(apache 2.4.18) on windows  when i access the
server on other pc and I have got en Error 403(you didn't have permission
to access on this server).I have changed the httpd.conf file following and
I also get the same error 403:

DocumentRoot "c:/wamp/www"

#
# Possible values for the Options directive are "None", "All",
# or any combination of:
#   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI
MultiViews
#
# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.
#
# The Options directive is both complicated and important.  Please see
# http://httpd.apache.org/docs/2.4/mod/core.html#options
# for more information.
#
Options +Indexes +FollowSymLinks

#
# AllowOverride controls what directives may be placed in .htaccess
files.
# It can be "All", "None", or any combination of the keywords:
#   AllowOverride FileInfo AuthConfig Limit
#
AllowOverride all

#
# Controls who can get stuff from this server.
#

#   onlineoffline tag - don't remove
 Require all granted