Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OC-FileId missing in COPY operation response #5039

Closed
jesmrec opened this issue Nov 11, 2022 · 7 comments
Closed

OC-FileId missing in COPY operation response #5039

jesmrec opened this issue Nov 11, 2022 · 7 comments
Assignees
Labels
Priority:p2-high Escalation, on top of current planning, release blocker QA:team Type:Bug

Comments

@jesmrec
Copy link

jesmrec commented Nov 11, 2022

Describe the bug

Android client expects the OC-FileId header in the response of the COPY operation.

Steps to reproduce

Steps to reproduce the behavior:

  1. Using Android client, copy a single file to another location. Or using the curl command:
curl -k -u admin:admin -H 'User-Agent:Mozilla/5.0 (Android) ownCloud-android/3.0-beta.2' -H 'Destination:https://xx.xx.xx.xx:9200/remote.php/dav/files/admin/A/1.txt'  -X COPY https://xx.xx.xx.xx:9200/remote.php/dav/files/admin/1.txt

Expected behavior

OC-FileId header returned in response with the file ID

Actual behavior

File is correctly copied, but the lack of OC-FileId header in response makes the Android client to display an ugly error. oC10 returns such header.

Setup

Please describe how you started the server and provide a list of relevant environment variables or configuration files.

Container created with the following docker-compose file:

version: "3.7"

services:
  ocis:
    image: owncloud/ocis:2.0.0-rc.1
    ports:
      - 9200:9200
      - 9215:9215
    environment:
      OCIS_INSECURE: "true"
      OCIS_URL: "https://xx.xx.xx.xx:9200"
      IDM_CREATE_DEMO_USERS: "true"
      IDM_ADMIN_PASSWORD: "admin"
      PROXY_ENABLE_BASIC_AUTH: "true"
    restart: "no"
    entrypoint:
      - /bin/sh
    # run ocis init to initialize a configuration file with random secrets
    # it will fail on subsequent runs, because the config file already exists
    # therefore we ignore the error and then start the ocis server
    command: ["-c", "ocis init || true; ocis server"]

Additional context

Add any other context about the problem here.

@micbar micbar added the Priority:p2-high Escalation, on top of current planning, release blocker label Nov 11, 2022
@micbar micbar added this to the 2.0.0 General Availability milestone Nov 11, 2022
@aduffeck aduffeck self-assigned this Nov 11, 2022
@individual-it
Copy link
Member

  • ToDo QA:Team: should be checked in an API test

@micbar
Copy link
Contributor

micbar commented Nov 15, 2022

Needs reva update. Removing from GA milestone.

@micbar micbar removed this from the 2.0.0 General Availability milestone Nov 15, 2022
@micbar micbar closed this as completed Nov 21, 2022
@SwikritiT
Copy link
Contributor

  • ToDo QA:Team: should be checked in an API test

Re-opening this as this is not done yet

@abelgardep
Copy link

Reopening

Fixed when copying files
Still missing the header when copying folders

@abelgardep abelgardep reopened this Feb 8, 2023
@github-project-automation github-project-automation bot moved this from Done to In progress in Infinite Scale Team Board Feb 8, 2023
@kobergj
Copy link
Collaborator

kobergj commented Feb 8, 2023

@aduffeck since you worked on the original PR (a century ago): Do you remember if it was a deliberate decision not to include the FileID when copying folders?

@aduffeck
Copy link
Contributor

aduffeck commented Feb 8, 2023

@kobergj how dare you, I'm not that old yet.. ;)

I don't think it was a deliberate decision, though, rather unawareness that folder operations are relevant as well.

@kobergj
Copy link
Collaborator

kobergj commented Mar 9, 2023

fixed on current master

@kobergj kobergj closed this as completed Mar 9, 2023
@github-project-automation github-project-automation bot moved this from In progress to Done in Infinite Scale Team Board Mar 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority:p2-high Escalation, on top of current planning, release blocker QA:team Type:Bug
Projects
Archived in project
Development

No branches or pull requests

8 participants