Dien-Foon Wu wrote:
> Yes, please remove the related address from the list for I am
> currently have no time to check these emails. Thanks.
> 2015-06-25 21:42 GMT+08:00 Hanns Mattes :
> >
> > Zitat von users-h...@httpd.apache.org:
To unsubscribe yourself: do it yourself: see footer & header.
Che
I have a test server on which we have a self-signed certificate. I get the
error "There is a problem with this website's security certificate." which
is expected because I'm using a self-signed cert. Normally I click on
"Continue to this website (not recommended)." and it goes through to my
websi
It looks like the Apache directive ...
ProxyErrorOverride
Allows the implementation of a custom error page within Apache/PHP-FPM
Similar in functionality to what "fastcgi_intercept_errors" does in nGinx.
Is that a correct observation? Any potential problems?
Thanks
From: , John Rose mailto:jb
I have seen this happen when you send an HSTS header. The Chrome error
would say that specifically.
A workaround would be to install that certificate on your system (with the
mmc certificate snap-in) so that it becomes a trusted certificate - trusted
site in IE is not enough.
- Y
On Fri, Jun 26,
Thanks for the response Yehuda. Unfortunately Chrome doesn't give me this
error. It just tells me that my connection isn't private. When I click on
advanced there is no option to go forward to the web server like I get on
some of the other servers I work with.
Larry Cohen
On Fri, Jun 26, 2015
When Chrome does not show the coninue option, it usually has an additional
error message where the button would be that shows more details.
For example, this is an HSTS error:
http://blogs.msdn.com/cfs-filesystemfile.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-47-13-metablogapi
Thank you. Chrome says "You cannot visit website xxx.yyy.com right now
because the website sent scrambled credentials that Chrome cannot process.
I'm not sure where these credentials are coming from, but I'm assuming this
is the .crt files in httpd/conf/ssl.crt.
Thanks,
Larry
On Fri, Jun 26, 20
That is a generic error message when Chrome does not have a more specific
error to show.
Something else I would try is to use something like the openssl command
line to verify the certificate.
You can use the command "openssl s_client -connect server_name:443" to have
OpenSSL tell you what certifi
Thank you. We now found a couple of other users which are able to get
through to the website, so now some of us can and some of us can't. I'm
guessing it has to be in the browsers of those of us who can't, but why
would we not be able to access from all browsers (IE, Firefox, Chrome)?
I'm extreme
On 06/25/2015 10:18 PM, Eric Covener wrote:
>>
>> Redirect /catalog/?app=ecom&ns=catshow&ref=books \
>> https://ya250.infusionsoft.com/app/storeFront/handleStoreFrontLink?displayType=Category&id=1&displayName=Books
>>
>
>>
> Redirect doesn't match against the query string. Try mod_rewrite.
>
On Fri, Jun 26, 2015 at 3:21 PM, James Moe wrote:
> RewriteCond %{QUERY_STRING} app=ecom&ns=catshow&ref=books
> RewriteRule ^
> https://ya250.infusionsoft.com/app/storeFront/handleStoreFrontLink?displayType=Category&id=1&displayName=Books
> [R=301,L]
RewriteRule matches aginstt just the path, wit
On Fri, Jun 26, 2015 at 12:34 PM, Eric Covener wrote:
> On Fri, Jun 26, 2015 at 3:21 PM, James Moe wrote:
> > RewriteCond %{QUERY_STRING} app=ecom&ns=catshow&ref=books
> > RewriteRule ^
> >
> https://ya250.infusionsoft.com/app/storeFront/handleStoreFrontLink?displayType=Category&id=1&displayName
On Fri, Jun 26, 2015 at 1:36 PM, Kurtis Rader wrote:
> My question for James would be how do you know the query string has the
> parameters in that exact order? Unless the query string has been
> hand-crafted you cannot assume the parameters will appear in any specific
> order. Also, your pattern
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/26/2015 01:36 PM, Kurtis Rader wrote:
> My question for James would be how do you know the query string has
> the parameters in that exact order?
>
That is how our current shopping cart generates an URL to locate a
page. It is completely predi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
apache 2.4.10
The mod_rewrite page mentions LogLevel as a useful way to trace
problems with ReWrite. So I added "LogLevel info
rewrite:trace5" to .htaccess and got "Internal Server Error".
What else is needed to get LogLevel to work?
- --
James
On Fri, Jun 26, 2015 at 4:12 PM, James Moe wrote:
> That is how our current shopping cart generates an URL to locate a
> page. It is completely predictable. I wish to match the Query String
> exactly as a string; I do not care about names and values.
> We are transitioning to another e-commer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/26/2015 06:36 PM, Kurtis Rader wrote:
> So I submit to you that either the query string is not in the form
> you expect or there is something else wrong with your
> configuration. For example, perhaps you have the rewrite rule in
> the wrong cont
17 matches
Mail list logo
