Bug 110649

Summary: freebusy trigger url hardcoded?
Product: [Applications] korganizer Reporter: andreas
Component: generalAssignee: kdepim bugs <pim-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: richard.bos, winter
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Mandriva RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description andreas 2005-08-12 19:50:24 UTC 
Version:           1.1.2 (using KDE KDE 3.4.2)
Installed from:    Mandriva RPMs
Compiler:          gcc-4.0.1 
OS:                Linux

I have a custom kolab2 installation which uses the /kolab prefix to URLs. So, for example, my freebusy url would start with http://kolabserver/kolab/freebusy instead of http://kolabserver/freebusy.

I configured this URL with /kolab in korganizer without problem. But I still see access without /kolab:
10.0.2.177 - - [12/Aug/2005:14:28:53 -0300] "GET /freebusy/trigger/sisko%40kolab.conectiva/Calendar.pfb HTTP/1.1" 404 1012

Notice it's using /freebusy instead of /kolab/freebusy which is what I configured in korganizer. So, is it hardcoded?

KMailICalIfaceImpl::triggerKolabFreeBusy in kmail/kmailicalifaceimpl.cpp seems to imply so:
(...)
    path = path.mid( secondSlash );
  }

  httpURL.setPath( "/freebusy/trigger/" + path + ".pfb" );
  httpURL.setQuery( QString::null );
  // Ensure that we encode everything with UTF8
  httpURL = KURL( httpURL.url(0,106), 106 );
  kdDebug() << "Triggering PFB update for " << folderURL << " : getting " << httpURL << endl;
(...)

If it is indeed hardcoded, then this should be changed to use the URL provided in korganizer's configuration dialog for freebusy.
Comment 1 Reinhold Kainhofer 2006-11-02 19:25:09 UTC 
Reassigning all KOrganizer bug reports and wishes to the newly created 
korganizer-devel mailing list.
Comment 2 Richard Bos 2009-01-18 21:21:34 UTC 
This looks related to:
https://bugs.kde.org/show_bug.cgi?id=177860
Comment 3 Allen Winter 2010-05-20 22:38:37 UTC 
... 5 years later.

this has been long since fixed, I believe.
you can add whatever URL you like in the KOrganizer configuration.

except that it will have "/email.ifb" appended.
I'm fixing that so it detects if the URL has an extension; if so, it uses the URL as entered into the configuration.

anyway closing this. reopen as needed.