Announcement

Collapse
No announcement yet.

Error 413 on MvCALL?

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

    Error 413 on MvCALL?

    Hi folks,

    I've written a custom payment module, and it's getting an Error 413 every time it tries to contact the gateway. I've been scratching my head on this one for some weeks, and I'm pretty stumped. Has anyone else ever seen this? If so, what did you do to fix it?

    We've turned on MvCALL logging in the VM, and it's not showing us any problems. Are there any other tools that we could use to get a more detailed picture of what the store is sending to the gateway?

    Thanks --
    Kent Multer
    Magic Metal Productions
    http://TheMagicM.com
    * Web developer/designer
    * E-commerce and Miva
    * Author, The Official Miva Web Scripting Book -- available on-line:
    http://www.amazon.com/exec/obidos/IS...icmetalproducA

    #2
    Re: Error 413 on MvCALL?

    How are you passing in the data? Using Post or Get? I think the logging you need to do is on the site being called.
    Bruce Golub
    Phosphor Media - "Your Success is our Business"

    Improve Your Customer Service | Get MORE Customers | Edit CSS/Javascript/HTML Easily | Make Your Site Faster | Get Indexed by Google | Free Modules | Follow Us on Facebook
    phosphormedia.com

    Comment


      #3
      Re: Error 413 on MvCALL?

      The module is doing MvCALL with METHOD="XML," which generates a POST.

      I agree, the gateway folks really ought to be able to tell us why their server is signalling this error. But they've been surprisingly un-helpful. They say, "none of our other users have this problem," and I say, "None of my other payment modules have this problem." Rather than let the situation devolve into a finger-pointing duel, I'm still looking for ways to find a solution.

      I know that there have been some changes to this part of the VM in recent months. My hunch is that there's some small compatibility issue between the VM and their server, something obscure enough that no one else has run into it yet. I've tested the module in two different stores -- the client's, and one of my test stores -- and got the same result on both.

      Thanks --
      Kent Multer
      Magic Metal Productions
      http://TheMagicM.com
      * Web developer/designer
      * E-commerce and Miva
      * Author, The Official Miva Web Scripting Book -- available on-line:
      http://www.amazon.com/exec/obidos/IS...icmetalproducA

      Comment


        #4
        Re: Error 413 on MvCALL?

        How big is the XML data you are submitting? A 413 error is "request entity too large". Maybe the wrong content-type?

        Comment


          #5
          Re: Error 413 on MvCALL?

          The XML isn't especially large, around 1K-2K bytes. The Content-type header is correct as far as I know; I've read it from the log and confirmed it with the gateway folks. Also, I think if we had an incorrect Content-type, we'd get an error message to that effect.

          413 is defined as "Request Entity Too Large" in the HTTP spec. I'm having trouble figuring out exactly what "Request Entity: means; too many false hits in the search engines. It seems like the most common cause of this error is that the request is physically too big for the server to read, e.g. if you accidentally uploaded a huge file with your POST. My module isn't doing anything like that.

          Thanks --
          Kent Multer
          Magic Metal Productions
          http://TheMagicM.com
          * Web developer/designer
          * E-commerce and Miva
          * Author, The Official Miva Web Scripting Book -- available on-line:
          http://www.amazon.com/exec/obidos/IS...icmetalproducA

          Comment

          Working...
          X