Reply
Highlighted
Member
Posts: 1
Registered: ‎10-28-2014

Re: AIM 403 Error using transact after Authorize updated SSL Certificate

We have been encountering the same issue - here's what we have discovered:

 

1) Any orders with an http POST of 1882 characters or less succeeds
2) Any orders with an http POST of 1883 characters or more returns the 403 error. 

 

Has anyone identified a tech support person at Authorize.net that is helpful?  I have an open support ticket, but we're not making much progress. 

 

Mary

 

Highlighted
Posts: 2,765
Topics: 57
Kudos: 247
Blog Posts: 67
Registered: ‎12-05-2011

Re: AIM 403 Error using transact after Authorize updated SSL Certificate

[ Edited ]

Hello @inxcapable 

 

Are you able to duplicate this in the sandbox?   If you can provide the support ticket number and Gateway ID, we can look into this further.

 

Richard

Highlighted
Posts: 321
Topics: 5
Kudos: 37
Blog Posts: 5
Ideas: 0
Solutions: 26
Registered: ‎11-09-2011

Re: AIM 403 Error using transact after Authorize updated SSL Certificate

@inxcapable We have the Gateway ID and ticket number now, and I'll bring this up to our developers. Thanks.

--
"Move fast and break things," out. "Move carefully and fix what you break," in.
Highlighted
Member
Posts: 7
Registered: ‎07-25-2014

Re: AIM 403 Error using transact after Authorize updated SSL Certificate

Was there any resolution to this? I thought capitalizing the POST would have resolved it but it did not.

Highlighted
Posts: 321
Topics: 5
Kudos: 37
Blog Posts: 5
Ideas: 0
Solutions: 26
Registered: ‎11-09-2011

Re: AIM 403 Error using transact after Authorize updated SSL Certificate

@ppatel How long is your POST string? 

 

As @inxcapable discovered, request strings over 1882 characters are causing HTTP 403s. Our developers will be looking into fixing this, but not until after the holiday season.

We find that the larger request strings are more common among merchants using the itemization features, and that in many cases it's possible to reduce the description of each line item to fit the request string into 1882 characters or less.

--
"Move fast and break things," out. "Move carefully and fix what you break," in.
Highlighted
Posts: 321
Topics: 5
Kudos: 37
Blog Posts: 5
Ideas: 0
Solutions: 26
Registered: ‎11-09-2011

Re: AIM 403 Error using transact after Authorize updated SSL Certificate

I apologize for not posting a follow-up sooner.

This situation recurred for another developer recently.

 

Upon investigation, we confirmed that, if you are using parameterized URLs, and thus submitting the info using HTTP GET rather than HTTP POST, you will run into HTTP 403 errors when exceeding 1800+ characters. (The exact character count depends on the size of your individual HTTP request headers, which in turn depend on the platform you're using.)

We strongly encourage any developers encountering similar issues, to switch to HTTP POST immediately. The legacy API guides had been previously updated to encourage using HTTP POST for submitting all transaction requests.

 

Note that this limitation only applies to using HTTP GET to submit transactions. The Authorize.Net API, documented at https://developer.authorize.net/api/reference/, only allows HTTP POST by default. Any future RESTful APIs we may release, will support HTTP GET for requesting service resources, but will require HTTP POST for submitting data in an API call.

 

Thanks.

--
"Move fast and break things," out. "Move carefully and fix what you break," in.