In theory 'http' error should only happen when a user cannot get an edit token (in this.postWithToken the deferred object must be rejected which only seems to happen if this.get( { action: 'tokens', type: type, assert: assert } ); either fails or returns a response with no token. @Anomie any idea why this might be happening?

In T97494#1246071, @Jdlrobson wrote:

this.get( { action: 'tokens', type: type, assert: assert } );

What are your values for "type" and "assert" there? In particular, if assert is "user" then you're going to get an error for every anon request ;)

Other than that, what's the specific API request query data? And are you sure there isn't some other source for "http" errors?

Moved this to In Sprint as this appears to be actively investigated.

This is the post that is happening on the client:

		var api = new mw.Api();
		api.postWithToken( {
					action: 'edit',
					title: self.title,
					prepend: '(text)',
					section: sectionId,
					summary: options.summary,
					captchaid: options.captchaId,
					captchaword: options.captchaWord,
					basetimestamp: self.timestamp,
					starttimestamp: self.timestamp
				} ).fail( $.proxy( result, 'reject', {
					type: 'error',
					details: 'http'
				} ) );

The deferred object is being rejected.
We'd have to do more investigation to find more about the parameters the users are sending.

In T97494#1253073, @Jdlrobson wrote:

					prependtext,

Really, no key?

					basetimestamp: self.timestamp,
					starttimestamp: self.timestamp

That doesn't seem right. starttimestamp is the time you started editing (e.g. when you fetched the current content to modify it), while basetimestamp is the timestamp of the revision you're editing.

If self.timestamp there is the revision timestamp, then you might be getting failures because the user is trying to edit a page that has been deleted since the timestamp of its top visible revision. If self.timestamp there is the start timestamp, I'm not sure what it'll do with getting a timestamp that doesn't correspond to a revision.

				} ).fail( $.proxy( result, 'reject', {
 					type: 'error',
 					details: 'http'
 				} ) );

So you're rejecting as "http" to your caller no matter why the API query actually failed? No wonder you're seeing a lot of "http" errors.

Task is supposedly in "current sprint" but not in either sprints so I've added it to both.

@Anomie the reject should only be reached if the API 404s or 500s etc.. there is a separate error handler in postWithToken for when the API responds with an error key.

The special error handler in postWithToken only handles badtoken errors. Any other error seems like it would be passed through to your handler and get turned into an "http" error.

Update:
This is still happening. In last two weeks [1]:

http 19581
ve-load-error 144
ve-save-error 235
Would be great to get to the bottom of these errors.

[1] select event_errorText, count(*) from MobileWebEditing_8599025 where event_action = 'error' and timestamp > 20150608000000 and event_username is NULL group by event_errorText

@Jdlrobson: It looks like we're going to have to separate out these errors: "http" could mean any number of things.

You're going to need to provide more information than just ve-(load|save)-error as well.

In T97494#1421590, @Krenair wrote:

You're going to need to provide more information than just ve-(load|save)-error as well.

Anybody able to provide that info? @Jdlrobson ?

In T97494#1421590, @Krenair wrote:

You're going to need to provide more information than just ve-(load|save)-error as well.

Anybody able to provide that info? @Jdlrobson ? Anyone else?

In T97494#1644747, @Aklapper wrote:

In T97494#1421590, @Krenair wrote:

You're going to need to provide more information than just ve-(load|save)-error as well.

Anybody able to provide that info? @Jdlrobson ? Anyone else?

Once T110272: Instrument MobileFrontend to use version 13457736 of the Edit schema instead of the MobileWebEditing schema is complete we'll have the more information, and be able to tell if the numbers are high in relative terms, as well as what their causes are.