I am using a php (curl) based PayPal express checkout script and it works just fine on my localhost and with GoDaddy server, however, with 1&1 server I just get a blank page.
I need to know how to set up a proxy in order to access the PayPal server.
I am new at this and would appreciate any help.
Best regards.
I finally found the answer myself. I placed these codes at the beginning of my pages that were concerned with the paypal checkout process.
ini_set('display_errors', 'on');
ini_set('log_errors', 1);
ini_set('error_reporting', E_ALL & ~E_NOTICE & ~E_STRICT & ~E_DEPRECATED);
As a result I found an error with the headers that were already posted.
I placed an
<?php ob_start();?>
at the beginning of all those pages and everything works just fine.
Related
Postman still sends to old sever although I updated its' variable. It works correctly on the web app. I've changed the server & linked the new server with the same sub-domain and deployed the same old app.
The windows app
The web app - works fine and it responds as it should
I changed the variable of the URL
I tried to create a new environment - didn't work
I tried to remove the entire workspace - didn't work
I un/re-installed the app - didn't work either
Is there a cache in the app itself or something to clear it to get the new value?
appreciate your help. T^T
An example to clarify my issue:
I have a subdomain: backend.mydomain.com
I've linked my server IP 152.50.133.60
so backend.mydomain.com points to -> 152.50.133.60
I made backend.mydomain.com free again to use it on a different server
Now I linked my new server IP 163.33.80.92
Now my backend.mydomain.com points to -> 163.33.80.92 & it works fine on (the postman web app & chrome)
When I try from PC app it still has the old value as in console pic
It worked after:
Signed Out.
Made a request not signed in.
Signed in again, then made a request it worked.
No clue why though!
One of my old website is running TYPO3 v4.5.
I bought a SSL certificate and my sys admin installed it on the server.
the front-end is running well on https
tha back-end login form runs weird : one time my login/password are ok, but sometimes it doesn't allow me to enter the back-end.
It is totally random and in Firebug, I have no clue in the console or in the network tab to help me. Same behavior for Chrome, FF or IE.
I tried a lot of parameters :
[BE]LockSSL = 1
[SYS][reverseProxyIP] with " ... "
[SYS][reverseProxySSL] with " * "
[SYS][cookieSecure] = 1
I event tried a lot of different combinations, with no success.
Please notice that I also get a TYPO3 6.2 website and those parameters work perfectly on it. I guess that I am missing somthing for v4.5 ?
Check the BE cookieDomain configuration!
This is an odd problem as all I'm trying to do is extend a configuration that is already happily functioning as described by adding a new web site, which is just a copy of an existing web application.
So what we have is a wildcard certificate *.business.com
We already have 8 other sites bound to the same SSL certificate each with their own host names.
a.business.com
b.business.com
..
h.business.com
All the existing sites are quite different in their role/application/structure so in that sense there aren't any duplicate files or applications.
I'm trying to add x.business.com and for some reason IIS does not want to know about it.
I'll explain what I've done and hopefully someone will see the erro of my ways.
My first step was to set an A record in the DNS for the domain.
So all the other URLs listed above all point to the same public IP address.
Lets call it 100.10.10.100
I then created a simple website in IIS with a simple default.htm for testing.
After setting the host name to x.business.com and binding the SSL certificate (using appcmd) I tested the site address. Nothing. By that I mean a generic error saying the site is unreachable. At this point there is no log as the site hasn't served anything.
A ping of the URL returns the IP address set in the DNS but no response.
To try and simplify I added another simple site called TestSite. I made an entry in the hosts file 127.0.0.1 TestSite. Tried the IIS server browser and this also didn't work.
However when I changed the TestSite to use port 81 and then tested http://testsite:81 I got a positive response.
I then tried to extend this test and made another A record testsite.business.com. Added the host name to the existing testsite and then tried http://testsite.business.com:81 it failed.
Rolling everything back and it worked again.
For the life of me I can't see what I need to do to get this working. It seems like a DNS issue but the other 8 sites are all working fine with the same IP address:port (eg 100.10.10.100:80), multiple sites bound to the same SSL certificate without issue and have been working from nearly two years.
I'd like to add I didn't set this up hence the groping around in the dark, but I'm sure I've done something similar in the past without issue.
I've searched for hours and have not found anything glaringly obvious that I've missed. it also worries me when I see few posts with similar issues it makes me think I'm missing something truly basic.
Your thoughts on diagnosing this issue are appreciated.
OK folks you can all relax.
Two issues a typo in the DNS A record. Yep that's on me.
However I also found an interesting piece of code in the default web site.
Default.asp has the following code. It appears this is doing a bit of translation of incoming web requests and redirection.
// Redirect appropriately
response.buffer = True
response.clear
response.status = "301 Moved"
If InStr(sServerName,"a") > 0 Then
response.addHeader "Location", "https://a.business.com/" & Request.QueryString
Elseif InStr(sServerName,"b") > 0 Then
response.addHeader "Location", "https://b.business.com/" & Request.QueryString
End If
So I added
// Redirect appropriately
response.buffer = True
response.clear
response.status = "301 Moved"
If InStr(sServerName,"a") > 0 Then
response.addHeader "Location", "https://a.business.com/" & Request.QueryString
Elseif InStr(sServerName,"b") > 0 Then
response.addHeader "Location", "https://b.business.com/" & Request.QueryString
Elseif InStr(sServerName,"x") > 0 Then
response.addHeader "Location", "https://x.business.com/" & Request.QueryString
End If
I inherited an existing project without its development environment. I have UAT code and a backup of the Production database. I can run up the site locally via Visual Studio but have hit an authentication problem trying to setup a fresh standalone DEV server on AWS (single server, no load balancer). The doco indicates the Prod server is a dual server setup with a load balancer.
The front end site pages do display, although some search is not working. On trying to log into the backend pages, Chrome returns "The xxx page isn't working. xxx redirected you too many times." Using developer tools, I can see the page redirects back and forth between SWT?realm=... and sitefinity?wrap_defalted=true&wrap_access_token... On the second redirect response header there is "X-Authentication-Error:Missing configuration for the issuer of security tokens 'https://xxx/Sitefinity/Authenticate/SWT' "
I tried different values in the web.config lines:
<federatedAuthentication>
<wsFederation passiveRedirectEnabled="true" issuer="http://localhost" realm="http://localhost" requireHttps="true"/>
<cookieHandler requireSsl="false"/>
</federatedAuthentication>
but that actually made things worse so I have reverted.
I checked all the settings mentioned in http://docs.sitefinity.com/administration-switch-to-claims-based-authentication and they seem to be set correctly. I don't really know what else I can check to get this working.
I found http://docs.sitefinity.com/administration-configure-security, but it does not seem like these settings are set (I don't have access to Prod server so can't confirm if it is actually setup with load balancing). I am currently using a 30 day trial license so am not sure if this is contributing to the problem. The official license is in the process of being transferred by the client. The domain name associated with the official license would be different to the domain my new server is currently running on.
I am also running version 8 code on a version 9 install of Sitefinity. I wanted to get it working before I tried to upgrade the code. I think there was also an assembly load to manifest mismatch when I tried upgrading my local version.
Found the solution: Don't mess with the SecurityConfig.config file.
<securityTokenIssuers>
<add key="B886AA7BFB5515BA63F577A44BBEB5C7AE674035514D128BC397346B11F4C97A" encoding="Hexadecimal" membershipProvider="Default" realm="http://localhost" />
</securityTokenIssuers>
<relyingParties>
<add key="B886AA7BFB5515BA63F577A44BBEB5C7AE674035514D128BC397346B11F4C97A" encoding="Hexadecimal" realm="http://localhost" />
</relyingParties>
Even though it is running on a server, the above lines should still point to localhost. It seems like these only need to be edited if you have a multi-server setup with an entirely separate STS.
I initially changed it to match the new domain name, but after some experimentation around adding localhost and HTTP variations, it seems like it works best with just localhost.
Even when I changed the web.config entry above to use the new domain as the issuer instead of localhost and the SecureConfig.config to specify only the new domain as the realms, it didn't seem to work. I guess the authentication must try to hit localhost specifically.
We face the "net::ERR_INCOMPLETE_CHUNKED_ENCODING" errors on our production site and cant find any working solution. StackOverflow is full of questions on this subject and we tried this and that but no working solution found. Our system is based on Symfony2+PHP5.6+Apache 2.4.x running on CentOS7.
Symptoms are that app is working fine when server starts ... but after some time the browser reports "net::ERR_INCOMPLETE_CHUNKED_ENCODING" errors and doest show certain pages (because they are loaded incompletely). Restarting apache fixes this for some time but it appears again soon. StackOverflow contains a lot of different hints that doesnt help us to understand the source of the problem. Can anyone give us some REAL hint here?
After further investigation I found out that server sends incorrect content-lenght information to browser for some reasons and its the source of the error.
To adjust this I have enabled content gzipping by adding 'SetOutputFilter DEFLATE' to Apache config file see details here http://httpd.apache.org/docs/2.4/mod/mod_deflate.html . This simple setting caused 'ERR_INCOMPLETE_CHUNKED_ENCODING' error to disappear and apps are working correctly for now. Whats more by gzipping the content the bandwidth dropped significantly.
In the context of a Controller in Drupal 8 (works for Symfony Framework as well) this solution worked for me:
$response = new Response($form_markup, 200, array(
'Cache-Control' => 'no-cache',
));
$content = $response->getContent();
$contentLength = strlen($content);
$response->headers->set('Content-Length', $contentLength);
return $response;
Otherwise the response header 'Transfer-Encoding' got a value 'chunked'. This may be a problem for some browsers.