[Skip to main content](#vessel-content) # PayPal warning.. does this apply? ## - **[tedstrauss](/forum/user/541-tedstrauss "View tedstrauss's Profile")** - [![tedstrauss's Avatar](https://www.hikashop.com/media/kunena/core/svg/person.svg)](/forum/user/541-tedstrauss "View tedstrauss's Profile") Topic Author - [ Offline](/forum/user/541-tedstrauss) Less More - Posts: 35 - Thank you received: 1 - - 13 years 3 months ago [\#114392](#114392) by [tedstrauss](/forum/user/541-tedstrauss "View tedstrauss's Profile") *[PayPal warning.. does this apply?](/forum/2-general-talk-about-hikashop/85452-paypal-warning-does-this-apply#114392 "Hi Jérome/Nicolas etc... =========================================================================== In a bulletin dated October 18, 2011, we announced that we were going to expand the number of IP addresses for www.paypal.com to improve our site’s performance, scalability and availability. As part of this transition, we planned to discontinue support for HTTP 1.0 protocol starting October 7, 2013. We have recently identified that this change may impact the ability of some of our merchants to perform IPN (Instant Payment Notification) post-back validation or PDT (Payment Data Transfer) posts to www.paypal.com and ipnpb.paypal.com. This happens when the IPN or PDT scripts use HTTP 1.0 protocol and do not include the “Host: www.paypal.com” or “Host: ipnpb.paypal.com” header in the HTTP request. Additional Details Starting October 7, 2013, we will require all incoming requests to have a “Host” header which complies with HTTP 1.1 Specifications. This header was not required under HTTP 1.0. IPN and PDT scripts using HTTP 1.0 may start failing with “HTTP/1.0 400 Bad Request” errors after October 7, 2013, which will result in IPN messages not being validated successfully, or PDT scripts not being able to retrieve transaction information. Action Required before October 7, 2013 Merchants need to update their IPN and/or PDT scripts to use HTTP 1.1, and include the “Host” and “Connection: close” HTTP header in the IPN postback script. Example with Host as www.paypal.com (please make necessary changes if you are using ipnpb.paypal.com): ASP //Set values for the request back req.Method="POST"; req.Host="' www.paypal.com '"; req.ContentType="application/x-www-form-urlencoded"; Perl $req=HTTP::Request->new('POST', ' www.paypal.com/cgi-bin/webscr '); $req->content_type('application/x-www-form-urlencoded'); $req->header(Host=> ' www.paypal.com '); $req->header(Connection=> 'close'); PHP // post back to PayPal system to validate $header="POST /cgi-bin/webscr HTTP/1.1\r\n"; $header .="Content-Type: application/x-www-form-urlencoded\r\n"; $header .="Host: www.paypal.com\r\n"; $header .="Connection: close\r\n\r\n"; Java HttpsURLConnection uc=(HttpsURLConnection) u.openConnection(); uc.setDoOutput(true); uc.setRequestProperty("Content-Type","application/x-www-form-urlencoded"); uc.setRequestProperty("Host", " www.paypal.com "); uc.setRequestProperty("Connection", "Close"); The PayPal Sandbox has been configured to reject any HTTP requests without the “Host” header with HTTP 400 error. Merchants can use the Sandbox environment to certify the changes to their IPN and PDT scripts. For more information on PDT and IPN, please refer to www.paypal.com/pdt and www.paypal.com/ipn . For additional information or questions about this change, please contact PayPal's Merchant Technical Support team via www.paypal.com/mts . Sincerely, PayPal =========================================================================== Es-ce que le plugin d' Hikashop pour PayPal se sert de HTTP 1.0? et ou es ce que ceci nous concerne? Merci, Emmanuel. P.S.: This is maybe useful info to add to the PayPal plugin documentation page?")* was created by *[tedstrauss](/forum/user/541-tedstrauss "View tedstrauss's Profile")* Hi Jérome/Nicolas etc... =========================================================================== In a bulletin dated October 18, 2011, we announced that we were going to expand the number of IP addresses for [ www.paypal.com](http://www.paypal.com) to improve our site’s performance, scalability and availability. As part of this transition, we planned to discontinue support for HTTP 1.0 protocol starting October 7, 2013. We have recently identified that this change may impact the ability of some of our merchants to perform IPN (Instant Payment Notification) post-back validation or PDT (Payment Data Transfer) posts to [ www.paypal.com](http://www.paypal.com) and ipnpb.paypal.com. This happens when the IPN or PDT scripts use HTTP 1.0 protocol and do not include the “Host: [ www.paypal.com”](http://www.paypal.com%E2%80%9D) or “Host: ipnpb.paypal.com” header in the HTTP request. Additional Details Starting October 7, 2013, we will require all incoming requests to have a “Host” header which complies with HTTP 1.1 Specifications. This header was not required under HTTP 1.0. IPN and PDT scripts using HTTP 1.0 may start failing with “HTTP/1.0 400 Bad Request” errors after October 7, 2013, which will result in IPN messages not being validated successfully, or PDT scripts not being able to retrieve transaction information. Action Required before October 7, 2013 Merchants need to update their IPN and/or PDT scripts to use HTTP 1.1, and include the “Host” and “Connection: close” HTTP header in the IPN postback script. Example with Host as [ www.paypal.com](http://www.paypal.com) (please make necessary changes if you are using ipnpb.paypal.com): ASP //Set values for the request back req.Method="POST"; req.Host="'[ www.paypal.com](http://www.paypal.com)'"; req.ContentType="application/x-www-form-urlencoded"; Perl $req=HTTP::Request->new('POST', '[ www.paypal.com/cgi-bin/webscr](https://www.paypal.com/cgi-bin/webscr)'); $req->content_type('application/x-www-form-urlencoded'); $req->header(Host=> '[ www.paypal.com](http://www.paypal.com)'); $req->header(Connection=> 'close'); PHP // post back to PayPal system to validate $header="POST /cgi-bin/webscr HTTP/1.1\r\n"; $header .="Content-Type: application/x-www-form-urlencoded\r\n"; $header .="Host: www.paypal.com\r\n"; $header .="Connection: close\r\n\r\n"; Java HttpsURLConnection uc=(HttpsURLConnection) u.openConnection(); uc.setDoOutput(true); uc.setRequestProperty("Content-Type","application/x-www-form-urlencoded"); uc.setRequestProperty("Host", "[ www.paypal.com](http://www.paypal.com)"); uc.setRequestProperty("Connection", "Close"); The PayPal Sandbox has been configured to reject any HTTP requests without the “Host” header with HTTP 400 error. Merchants can use the Sandbox environment to certify the changes to their IPN and PDT scripts. For more information on PDT and IPN, please refer to [ www.paypal.com/pdt](http://www.paypal.com/pdt) and [ www.paypal.com/ipn](http://www.paypal.com/ipn). For additional information or questions about this change, please contact PayPal's Merchant Technical Support team via [ www.paypal.com/mts](https://www.paypal.com/mts). Sincerely, PayPal =========================================================================== Es-ce que le plugin d' Hikashop pour PayPal se sert de HTTP 1.0? et ou es ce que ceci nous concerne? Merci, Emmanuel. P.S.: This is maybe useful info to add to the PayPal plugin documentation page? Please [Log in](/login?return=aHR0cHM6Ly93d3cuaGlrYXNob3AuY29tL2ZvcnVtLzItZ2VuZXJhbC10YWxrLWFib3V0LWhpa2FzaG9wLzg1NDUyLXBheXBhbC13YXJuaW5nLWRvZXMtdGhpcy1hcHBseT90bXBsPW1hcmtkb3du) or [Create an account](/component/users/registration?Itemid=101) to join the conversation. - **[Jerome](/forum/user/80-jerome "View Jerome's Profile")** - [![Jerome's Avatar](https://www.hikashop.com/media/kunena/avatars/resized/size144/users/avatar80.png)](/forum/user/80-jerome "View Jerome's Profile") - [ Offline](/forum/user/80-jerome) - HikaShop core developer Less More - Posts: 26394 - Thank you received: 4078 - - [](http://obsi.dev) - 13 years 3 months ago [\#114405](#114405) by [Jerome](/forum/user/80-jerome "View Jerome's Profile") Replied by *[Jerome](/forum/user/80-jerome "View Jerome's Profile")* on topic *[PayPal warning.. does this apply?](/forum/2-general-talk-about-hikashop/85452-paypal-warning-does-this-apply#114405 "Hi Jérome/Nicolas etc... =========================================================================== In a bulletin dated October 18, 2011, we announced that we were going to expand the number of IP addresses for www.paypal.com to improve our site’s performance, scalability and availability. As part of this transition, we planned to discontinue support for HTTP 1.0 protocol starting October 7, 2013. We have recently identified that this change may impact the ability of some of our merchants to perform IPN (Instant Payment Notification) post-back validation or PDT (Payment Data Transfer) posts to www.paypal.com and ipnpb.paypal.com. This happens when the IPN or PDT scripts use HTTP 1.0 protocol and do not include the “Host: www.paypal.com” or “Host: ipnpb.paypal.com” header in the HTTP request. Additional Details Starting October 7, 2013, we will require all incoming requests to have a “Host” header which complies with HTTP 1.1 Specifications. This header was not required under HTTP 1.0. IPN and PDT scripts using HTTP 1.0 may start failing with “HTTP/1.0 400 Bad Request” errors after October 7, 2013, which will result in IPN messages not being validated successfully, or PDT scripts not being able to retrieve transaction information. Action Required before October 7, 2013 Merchants need to update their IPN and/or PDT scripts to use HTTP 1.1, and include the “Host” and “Connection: close” HTTP header in the IPN postback script. Example with Host as www.paypal.com (please make necessary changes if you are using ipnpb.paypal.com): ASP //Set values for the request back req.Method="POST"; req.Host="' www.paypal.com '"; req.ContentType="application/x-www-form-urlencoded"; Perl $req=HTTP::Request->new('POST', ' www.paypal.com/cgi-bin/webscr '); $req->content_type('application/x-www-form-urlencoded'); $req->header(Host=> ' www.paypal.com '); $req->header(Connection=> 'close'); PHP // post back to PayPal system to validate $header="POST /cgi-bin/webscr HTTP/1.1\r\n"; $header .="Content-Type: application/x-www-form-urlencoded\r\n"; $header .="Host: www.paypal.com\r\n"; $header .="Connection: close\r\n\r\n"; Java HttpsURLConnection uc=(HttpsURLConnection) u.openConnection(); uc.setDoOutput(true); uc.setRequestProperty("Content-Type","application/x-www-form-urlencoded"); uc.setRequestProperty("Host", " www.paypal.com "); uc.setRequestProperty("Connection", "Close"); The PayPal Sandbox has been configured to reject any HTTP requests without the “Host” header with HTTP 400 error. Merchants can use the Sandbox environment to certify the changes to their IPN and PDT scripts. For more information on PDT and IPN, please refer to www.paypal.com/pdt and www.paypal.com/ipn . For additional information or questions about this change, please contact PayPal's Merchant Technical Support team via www.paypal.com/mts . Sincerely, PayPal =========================================================================== Es-ce que le plugin d' Hikashop pour PayPal se sert de HTTP 1.0? et ou es ce que ceci nous concerne? Merci, Emmanuel. P.S.: This is maybe useful info to add to the PayPal plugin documentation page?")* Hi, The plugins will be update in the next packages. We use the "host" but we do not have the "http 1.1". I tried to find something in the documentation but... Like always, it is just impossible to have something (or something clear). Regards and thanks for the share --- Jerome - Obsidev.com HikaMarket & HikaSerial developer / HikaShop core dev team. Please [Log in](/login?return=aHR0cHM6Ly93d3cuaGlrYXNob3AuY29tL2ZvcnVtLzItZ2VuZXJhbC10YWxrLWFib3V0LWhpa2FzaG9wLzg1NDUyLXBheXBhbC13YXJuaW5nLWRvZXMtdGhpcy1hcHBseT90bXBsPW1hcmtkb3du) or [Create an account](/component/users/registration?Itemid=101) to join the conversation. - **[vboz](/forum/user/21341-vboz "View vboz's Profile")** - [![vboz's Avatar](https://www.hikashop.com/media/kunena/core/svg/person.svg)](/forum/user/21341-vboz "View vboz's Profile") - [ Offline](/forum/user/21341-vboz) Less More - Posts: 12 - Thank you received: 0 - - 13 years 1 month ago [\#120301](#120301) by [vboz](/forum/user/21341-vboz "View vboz's Profile") Replied by *[vboz](/forum/user/21341-vboz "View vboz's Profile")* on topic *[PayPal warning.. does this apply?](/forum/2-general-talk-about-hikashop/85452-paypal-warning-does-this-apply#120301 "Hi Jérome/Nicolas etc... =========================================================================== In a bulletin dated October 18, 2011, we announced that we were going to expand the number of IP addresses for www.paypal.com to improve our site’s performance, scalability and availability. As part of this transition, we planned to discontinue support for HTTP 1.0 protocol starting October 7, 2013. We have recently identified that this change may impact the ability of some of our merchants to perform IPN (Instant Payment Notification) post-back validation or PDT (Payment Data Transfer) posts to www.paypal.com and ipnpb.paypal.com. This happens when the IPN or PDT scripts use HTTP 1.0 protocol and do not include the “Host: www.paypal.com” or “Host: ipnpb.paypal.com” header in the HTTP request. Additional Details Starting October 7, 2013, we will require all incoming requests to have a “Host” header which complies with HTTP 1.1 Specifications. This header was not required under HTTP 1.0. IPN and PDT scripts using HTTP 1.0 may start failing with “HTTP/1.0 400 Bad Request” errors after October 7, 2013, which will result in IPN messages not being validated successfully, or PDT scripts not being able to retrieve transaction information. Action Required before October 7, 2013 Merchants need to update their IPN and/or PDT scripts to use HTTP 1.1, and include the “Host” and “Connection: close” HTTP header in the IPN postback script. Example with Host as www.paypal.com (please make necessary changes if you are using ipnpb.paypal.com): ASP //Set values for the request back req.Method="POST"; req.Host="' www.paypal.com '"; req.ContentType="application/x-www-form-urlencoded"; Perl $req=HTTP::Request->new('POST', ' www.paypal.com/cgi-bin/webscr '); $req->content_type('application/x-www-form-urlencoded'); $req->header(Host=> ' www.paypal.com '); $req->header(Connection=> 'close'); PHP // post back to PayPal system to validate $header="POST /cgi-bin/webscr HTTP/1.1\r\n"; $header .="Content-Type: application/x-www-form-urlencoded\r\n"; $header .="Host: www.paypal.com\r\n"; $header .="Connection: close\r\n\r\n"; Java HttpsURLConnection uc=(HttpsURLConnection) u.openConnection(); uc.setDoOutput(true); uc.setRequestProperty("Content-Type","application/x-www-form-urlencoded"); uc.setRequestProperty("Host", " www.paypal.com "); uc.setRequestProperty("Connection", "Close"); The PayPal Sandbox has been configured to reject any HTTP requests without the “Host” header with HTTP 400 error. Merchants can use the Sandbox environment to certify the changes to their IPN and PDT scripts. For more information on PDT and IPN, please refer to www.paypal.com/pdt and www.paypal.com/ipn . For additional information or questions about this change, please contact PayPal's Merchant Technical Support team via www.paypal.com/mts . Sincerely, PayPal =========================================================================== Es-ce que le plugin d' Hikashop pour PayPal se sert de HTTP 1.0? et ou es ce que ceci nous concerne? Merci, Emmanuel. P.S.: This is maybe useful info to add to the PayPal plugin documentation page?")* Will there be some sort of notification when the updated plug-in is available? I want to make sure to install it before Oct. 7 and not have any problems. Thank you! Please [Log in](/login?return=aHR0cHM6Ly93d3cuaGlrYXNob3AuY29tL2ZvcnVtLzItZ2VuZXJhbC10YWxrLWFib3V0LWhpa2FzaG9wLzg1NDUyLXBheXBhbC13YXJuaW5nLWRvZXMtdGhpcy1hcHBseT90bXBsPW1hcmtkb3du) or [Create an account](/component/users/registration?Itemid=101) to join the conversation. - **[Jerome](/forum/user/80-jerome "View Jerome's Profile")** - [![Jerome's Avatar](https://www.hikashop.com/media/kunena/avatars/resized/size144/users/avatar80.png)](/forum/user/80-jerome "View Jerome's Profile") - [ Offline](/forum/user/80-jerome) - HikaShop core developer Less More - Posts: 26394 - Thank you received: 4078 - - [](http://obsi.dev) - 13 years 1 month ago [\#120307](#120307) by [Jerome](/forum/user/80-jerome "View Jerome's Profile") Replied by *[Jerome](/forum/user/80-jerome "View Jerome's Profile")* on topic *[PayPal warning.. does this apply?](/forum/2-general-talk-about-hikashop/85452-paypal-warning-does-this-apply#120307 "Hi Jérome/Nicolas etc... =========================================================================== In a bulletin dated October 18, 2011, we announced that we were going to expand the number of IP addresses for www.paypal.com to improve our site’s performance, scalability and availability. As part of this transition, we planned to discontinue support for HTTP 1.0 protocol starting October 7, 2013. We have recently identified that this change may impact the ability of some of our merchants to perform IPN (Instant Payment Notification) post-back validation or PDT (Payment Data Transfer) posts to www.paypal.com and ipnpb.paypal.com. This happens when the IPN or PDT scripts use HTTP 1.0 protocol and do not include the “Host: www.paypal.com” or “Host: ipnpb.paypal.com” header in the HTTP request. Additional Details Starting October 7, 2013, we will require all incoming requests to have a “Host” header which complies with HTTP 1.1 Specifications. This header was not required under HTTP 1.0. IPN and PDT scripts using HTTP 1.0 may start failing with “HTTP/1.0 400 Bad Request” errors after October 7, 2013, which will result in IPN messages not being validated successfully, or PDT scripts not being able to retrieve transaction information. Action Required before October 7, 2013 Merchants need to update their IPN and/or PDT scripts to use HTTP 1.1, and include the “Host” and “Connection: close” HTTP header in the IPN postback script. Example with Host as www.paypal.com (please make necessary changes if you are using ipnpb.paypal.com): ASP //Set values for the request back req.Method="POST"; req.Host="' www.paypal.com '"; req.ContentType="application/x-www-form-urlencoded"; Perl $req=HTTP::Request->new('POST', ' www.paypal.com/cgi-bin/webscr '); $req->content_type('application/x-www-form-urlencoded'); $req->header(Host=> ' www.paypal.com '); $req->header(Connection=> 'close'); PHP // post back to PayPal system to validate $header="POST /cgi-bin/webscr HTTP/1.1\r\n"; $header .="Content-Type: application/x-www-form-urlencoded\r\n"; $header .="Host: www.paypal.com\r\n"; $header .="Connection: close\r\n\r\n"; Java HttpsURLConnection uc=(HttpsURLConnection) u.openConnection(); uc.setDoOutput(true); uc.setRequestProperty("Content-Type","application/x-www-form-urlencoded"); uc.setRequestProperty("Host", " www.paypal.com "); uc.setRequestProperty("Connection", "Close"); The PayPal Sandbox has been configured to reject any HTTP requests without the “Host” header with HTTP 400 error. Merchants can use the Sandbox environment to certify the changes to their IPN and PDT scripts. For more information on PDT and IPN, please refer to www.paypal.com/pdt and www.paypal.com/ipn . For additional information or questions about this change, please contact PayPal's Merchant Technical Support team via www.paypal.com/mts . Sincerely, PayPal =========================================================================== Es-ce que le plugin d' Hikashop pour PayPal se sert de HTTP 1.0? et ou es ce que ceci nous concerne? Merci, Emmanuel. P.S.: This is maybe useful info to add to the PayPal plugin documentation page?")* Hi, You can re-download HikaShop 2.2.0, the latest package contains the update of the paypal plugin. You can also wait a little, we will release 2.2.1 during the week end. Regards, --- Jerome - Obsidev.com HikaMarket & HikaSerial developer / HikaShop core dev team. Please [Log in](/login?return=aHR0cHM6Ly93d3cuaGlrYXNob3AuY29tL2ZvcnVtLzItZ2VuZXJhbC10YWxrLWFib3V0LWhpa2FzaG9wLzg1NDUyLXBheXBhbC13YXJuaW5nLWRvZXMtdGhpcy1hcHBseT90bXBsPW1hcmtkb3du) or [Create an account](/component/users/registration?Itemid=101) to join the conversation. Board Categories HikaShop- Install & Update- Product & Category Display- Content Creation- Sales and Orders- - Orders management- - Reports & Statistics- Customers- Checkout- Payment Methods- Shipping Methods- Import & Export (CSV, XLS…)- Specific Features- - Affilation- - Taxes- - Wishlist- - Vote- - Carousel & Slider- - Mass Actions- - Filters & Search- - Discount & Coupon- - Feature Request- Integrations- Showcase- General Talk about HikaShop- Development- - HikaShop 3.0 Beta- Translation- Commercial Jobs HikaShop Components- HikaMarket- - Market: Feature requests- - Market: How to?- - Market: Bug Report- HikaSerial- - General talk about HikaSerial- - Serial: Bug Report- - Serial: How to?- - Support en Français de HikaSerial (French Support)- - HikaSubscription- HikaAuction- - Auction: Feature requests- - Auction: How to?- - Auction: Bug report Hikashop around the world- Support en Français (French Support)- Russian- - FAQ. Курс выживания с Hikashop. Частые вопросы и о- - Расширения Hikashop- - Наши сайты на Hikashop- 日本語版サポート(Japanese Support)- Thai- German Archives- Bug Report- How to? [](/forum/topics/feed/mode-topics?format=feed&type=rss) Time to create page: 0.147 seconds [Powered by](/forum/credits) [Kunena Forum](https://www.kunena.org) [](#top)