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

Dislike the "index.php" in the sharing URL of ownCloud #1047

Closed
bogao opened this issue Dec 20, 2016 · 8 comments
Closed

Dislike the "index.php" in the sharing URL of ownCloud #1047

bogao opened this issue Dec 20, 2016 · 8 comments

Comments

@bogao
Copy link

bogao commented Dec 20, 2016

Can the new version of MIAB deliver a new nginx configuration so that the URL can look better?
screenshot_20161221_001004

@jvolkenant
Copy link
Contributor

This may be possible via https://doc.owncloud.org/server/9.0/admin_manual/configuration_server/index_php_less_urls.html#configuration-steps

But if the old URL's stop working that would be a problem and having two urls would only complicate matters.

@bogao
Copy link
Author

bogao commented Jan 2, 2017

Those instructions are for Apache configuration. As far as I remember MIAB is using nginx, for which it is claimed that no extra configuration steps are required?

@azzamsa
Copy link

azzamsa commented Jul 20, 2020

any update on this?

I've installed the latest version of MIAB, but nexcloud sharing URL still contains "index.php"

@JoshData
Copy link
Member

If someone does the work to make the change and ensure it doesn't break any existing uses and users of Mail-in-a-Box, I would consider it, of course, but it seems unlikely that will happen.

@azzamsa
Copy link

azzamsa commented Jul 21, 2020

Thanks for the response. I don't think I've that capability currently.

@Synchro
Copy link
Contributor

Synchro commented Jul 21, 2020

Looking at the config recommended in Nextcloud (16) docs, there are quite a few differences from what's in MIAB (beyond /cloud vs /nextcloud). At a guess, I'd say the current MIAB config looks like an older config. Is there any particular reason not to copy that config as-is?

@JoshData
Copy link
Member

JoshData commented Aug 1, 2020

Is there any particular reason not to copy that config as-is?

That's not a question that can be answered without doing some work to compare it and research what each directive is for. If you ask a more specific question about it, I can try to answer.

@dumblob
Copy link

dumblob commented Aug 31, 2020

@Synchro did you find some time for comparison to decide whether the new configuration would solve the issue described in the very first post?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants