search

owncloud / contacts

:busts_in_silhouette: Manage your CardDAV contacts from a feature-rich web-interface
75 stars 46 forks source link

HTTP error code 412 when trying to add/update a contact #697

Open Oktopuce opened 4 years ago

Oktopuce commented 4 years ago

Hi,

Steps to reproduce

  1. Click on "New contact"
  2. Set the name
  3. Set another field

Expected behaviour

All fields for contact must be automatically saved when they are filled.

Actual behaviour

The first field is saved (so far so good) but other fields are not (HTTP error code 412). I inspected network requests and have seen that for the second and next call to .vcf, the content is encoding with gzip (have a look at screen capture). It works well on another server so I think it depends on the server configuration but don't know how to solve it.

OwnCloud - Response 204 OwnCloud - Response 412

Server configuration

Operating system: Linux

Web server:

Database: MySQL 5.5

PHP version: 7.2

ownCloud version: (see ownCloud admin page) v10.4.1

Contacts version: (see ownCloud apps page) 1.5.5

Updated from an older ownCloud or fresh install: Fresh install

Signing status (ownCloud 9.0 and above):


Login as admin user into your ownCloud and access 
http://example.com/index.php/settings/integrity/failed 
paste the results here.
No errors have been found.

**
**Are you using external storage, if yes which one:** local/smb/sftp/...
No
**Are you using encryption:** yes/no
Yes
**Are you using an external user-backend, if yes which one:** LDAP/ActiveDirectory/Webdav/...
No
DeepDiver1975 commented 4 years ago

If I remember correctly this happens when the requests for saving are sent too fast to the server. An easy workaround is to wait a bit.

Furthermore I'm sorry to say but there is nobody working on this app anymore. It is very unlikely that a fix will arrive. :man_shrugging:

Oktopuce commented 4 years ago

Thanks Thomas for your answer but its' not the case, I've tried to wait but the problem remains. But it strange, on a local machine, it works well and I noticed that there is no gzip header content encoding. May be you know how to disable gzip in script.js or in .htaccess ?

DeepDiver1975 commented 4 years ago

A different content-type (and resulting a different content-encoding) is quite expected. The 204 response has no response body where the 412 response has a body holding xml.

Please post the response body - maybe we find something quickly.