I'm using the default REST server with session auth, didn't change a thing,
after updating to 3.5 every service call, even "system/connect" return a weird hashed string:
"pqUr2W2-ZpgiVTVLNaE5f0zgLtUGEj_twjLGtEAHsTQ"

Comments

kylebrowning’s picture

kylebrowning commented

Can confirm, someone broke services releases.

stupiddingo’s picture

stupiddingo commented

Not sure if this is related, but I found on updating UUID (which I updated with Services) that the default behavior of UUID_Services module changed all REST requests from node/nid to node/uuid. All requests via nid, tid or uid returned only [false].

This doesn't match the behavior OP describes, but may help others who land here. Once I fixed my URLs to match everything was firing again using Services 3.4 or 3.5.

bruce.wins’s picture

bruce.wins commented

Same here except GET requests still seem to work, but POST requests only return 404. I also upgraded to D7.23 the same day.

I have two servers set up exactly the same, just creating simple nodes with a title and body with REST and application/xml. The one that I updated just doesn't accept POST anymore.

ygerasimov’s picture

ygerasimov commented

Please advise how to reproduce the problem? I have Services 3.5. What call is failing?

@bruce.wins what error message do you get while doing POST requests?

marcingy’s picture

marcingy commented
Priority: Critical » Normal
Status: Active » Postponed (maintainer needs more info)
kylebrowning’s picture

kylebrowning commented
Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)