Announcement

Collapse
No announcement yet.

HTTP protocol level for MvCALL - 1.0 or 1.1

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    HTTP protocol level for MvCALL - 1.0 or 1.1

    All the documentation for MvCALL that I can find says it operates on HTTP 1.0 protocol. PayPal has announced that on March 25th they will upgrade their system and all HTTP 1.0 protocols will no longer be supported and return an HTTP/1.0 400 Bad Request.

    Can anyone confirm the protocal level for MvCall?

    My current Miva version is 5.19

    Thanks
    DonB
    Don Barnett
    Farm & Home Supply Center

    #2
    Re: HTTP protocol level for MvCALL - 1.0 or 1.1

    We're working with paypal to get an exception on this until much later in 2014. As of now there's no way to do http 1.1 with Mivascrip and it will require a new Miva Empresa engine from our end.
    Thanks,

    Rick Wilson
    CEO
    Miva, Inc.
    [email protected]
    https://www.miva.com

    Comment


      #3
      Re: HTTP protocol level for MvCALL - 1.0 or 1.1

      Thanks for the reply. That is going to be a real big problem for us who do not run Merchant. Is the exception you are working on going to include custom applications written in Miva but not running Merchant?

      Thanks
      DonB
      Don Barnett
      Farm & Home Supply Center

      Comment


        #4
        Re: HTTP protocol level for MvCALL - 1.0 or 1.1

        I'm not sure how PayPal would track the exceptions (or even why they're doing this). So you use Mivascript to connect to PayPal but not through Miva Merchant?
        Thanks,

        Rick Wilson
        CEO
        Miva, Inc.
        [email protected]
        https://www.miva.com

        Comment


          #5
          Re: HTTP protocol level for MvCALL - 1.0 or 1.1

          That is correct. I use the MvCall to call the paypal api in my custom cart which has been running for many years. The paypal api was added about a year ago and has worked great so I don't understand why they are doing this either. I depend very heavily on that interface so I guess I am going to have to get creative.
          Don Barnett
          Farm & Home Supply Center

          Comment


            #6
            Re: HTTP protocol level for MvCALL - 1.0 or 1.1

            Don,

            I can't promise anything but if you'll send me an email with your details and situation I'll talk to my PayPal people about it.
            Thanks,

            Rick Wilson
            CEO
            Miva, Inc.
            [email protected]
            https://www.miva.com

            Comment


              #7
              Re: HTTP protocol level for MvCALL - 1.0 or 1.1

              I'm in the same boat... I have a custom built website that uses Paypal IPN for member fees.

              Keep us updated with how the negotiations the PayPal go.

              Comment


                #8
                Re: HTTP protocol level for MvCALL - 1.0 or 1.1

                Will do.
                Thanks,

                Rick Wilson
                CEO
                Miva, Inc.
                [email protected]
                https://www.miva.com

                Comment


                  #9
                  Re: HTTP protocol level for MvCALL - 1.0 or 1.1

                  Don,

                  Can you post a link to where you got this information? I don't see an email regarding this, and in my web searching for an answer, I've seen dates that this switch-over will happen anywhere from Oct 2012 on.

                  Just for my peace of mind, and as a starting point to reach out to PayPal directly, I'd like to read this announcement from PayPal directly.

                  Thanks

                  Comment


                    #10
                    Re: HTTP protocol level for MvCALL - 1.0 or 1.1

                    I actually don't have a link.
                    Thanks,

                    Rick Wilson
                    CEO
                    Miva, Inc.
                    [email protected]
                    https://www.miva.com

                    Comment


                      #11
                      Re: HTTP protocol level for MvCALL - 1.0 or 1.1

                      Her is the text of the message I received from PayPal on Monday Feb 10, 2014. Hope this helps.
                      Don

                      REMINDER: PAYPAL SERVICE UPGRADES

                      ***Please do not disregard this email. Failure to make necessary changes to your PayPal integration may result in an inability to make API calls and/or receive payments through PayPal.
                      PayPal continues to make significant investments and improvements to its infrastructure to improve our performance, scalability and availability to our customers. These improvements sometimes require us to perform necessary site maintenance upgrades. These upgrades sometimes require merchants to make changes to or update their existing integration.
                      Please make sure you are ready for this event by consulting with your technology team or individual(s) responsible for your PayPal integration.
                      What's happening?

                      Because of a system upgrade, the following API endpoints are being updated:
                      " api.paypal.com
                      " api-3t.paypal.com
                      " svcs.paypal.com

                      When is this happening?
                      This event is scheduled for the following date(s) and time(s):
                      " Date: March 25, 2014
                      " Time: 11:00 p.m. Pacific Daylight Time (PDT)

                      Why is this happening?
                      We are performing this upgrade to ensure more efficient services for PayPal API users.

                      What do I need to do?
                      Merchants integrated in the following non-standard ways with PayPal's API calls will be impacted when we update the API endpoints:
                      " Merchants calling our APIs with a hardcoded PayPal API endpoint IP address rather than using DNS resolution. See section A below.
                      " Merchants using HTTP methods other than GET, POST, DELETE and PUT. See section B below.
                      " Merchants using the HTTP 1.0 protocol. See section C below.
                      " Merchants whose firewall is configured to allow incoming and/or outgoing traffic from only a specific set of IP addresses will need to reconfigure their integration. See section D below.
                      ***If you are integrated with a partner or a cart, please visit this FAQ for more important information.

                      Action items
                      Your technical team or individual(s) responsible for your PayPal integration will need to examine your current integration and make necessary changes.
                      Below are merchant action items for each of the impacts listed above:
                      A. Merchants calling our APIs with a hardcoded PayPal API endpoint IP address rather than using DNS resolution
                      o Impact to your business: API calls will timeout or the merchant will encounter an internal error from their system
                      o Your call to action: Use DNS resolution to access our API endpoints and/or open your firewall to the new IP addresses which will be communicated
                      B. Merchants using HTTP methods other than GET, POST, DELETE and PUT:
                      o Impact to your business: API calls will return HTTP/1.0 400 Bad Request or HTTP Error 405 Method not allowed
                      o Your call to action: Send the API requests using one of the allowed methods. Heartbeat calls using the HEAD method will not be allowed
                      C. Merchants using the HTTP 1.0 protocol:
                      o Impact to your business: API calls will return HTTP/1.0 400 Bad Request
                      o Your call to action: Merchants should update their code to HTTP 1.1 and include the Host header in the API request
                      D. Merchants needing firewall changes to allow new IP addresses:
                      o Impact to your business: API calls will error out for merchants whose system responsible for making API calls to PayPal is behind a firewall that uses Access Control List (ACL) rules, and restricts outbound traffic to a limited number of IP addresses.
                      o Your call to action: You need to update your firewall ACL to allow outbound access to a new set of IP addresses we will be publishing. Test your integration on Sandbox (the IP addresses for Sandbox API endpoints are listed here). The list of new IP addresses for our Live API endpoints can be found here.
                      To assist with any questions you may have, we have an FAQ available here.
                      For additional details of this event, please refer to this blog. Please note that maintenance events can be postponed, rescheduled or cancelled so it's important that you review this information periodically.
                      If you have any questions, please contact PayPal Merchant Technical Services by filing a ticket; refer to LIVE API integration change in preparation for March 25. For real time system updates, please go to www.paypal.com/sitestatus.
                      Thank you for your understanding.
                      Sincerely,
                      PayPal
                      Keep up-to-date with the latest technical information on our new portal www.PayPal-Notify.com. The portal will give you everything you need to know about planned site maintenances, unplanned events, and site changes. Just sign up using your PayPal, Google, Yahoo or Facebook account login details.
                      Don Barnett
                      Farm & Home Supply Center

                      Comment


                        #12
                        Re: HTTP protocol level for MvCALL - 1.0 or 1.1

                        I've personally received same Email. Here is a posting on "one of the other platforms forum" that shows the complete Email contents:

                        http://forums.oscommerce.com/topic/3...rch-25th-2014/

                        Comment


                          #13
                          Re: HTTP protocol level for MvCALL - 1.0 or 1.1

                          Just to be sure I checked with PayPal and they verified that the Mar 25, 2014 date is correct and they will be making their system upgrade on that day.

                          Don
                          Don Barnett
                          Farm & Home Supply Center

                          Comment


                            #14
                            Re: HTTP protocol level for MvCALL - 1.0 or 1.1

                            What they're not telling you is they have the ability to "whitelist" some partners as ok on HTTP 1.0 until the end of Q3 2014. What's not clear is if that's based on Server IP, Partner Code, Programming language, or some other undetermined thing.
                            Thanks,

                            Rick Wilson
                            CEO
                            Miva, Inc.
                            [email protected]
                            https://www.miva.com

                            Comment


                              #15
                              Re: HTTP protocol level for MvCALL - 1.0 or 1.1

                              I talked with PayPal Support this morning and they said that the only white listing that will be done (if at all) will be with "Partners" who can demonstrate a critical need. They will NOT be white listing individual sites. They also indicated that they have moved this date out several times and that it is pretty set in stone at this time. I guess it is time to develop some kind of replacement for the MvCalls to PayPal. YUK! That certainly was not in my plans for this year.

                              DonB
                              Don Barnett
                              Farm & Home Supply Center

                              Comment

                              Working...
                              X